From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 8289 invoked by alias); 23 Jun 2005 15:28:50 -0000 Mailing-List: contact ecos-discuss-help@ecos.sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: ecos-discuss-owner@ecos.sourceware.org Received: (qmail 8265 invoked by uid 22791); 23 Jun 2005 15:28:46 -0000 Received: from omr1.netsolmail.com (HELO omr1.netsolmail.com) (216.168.230.162) by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Thu, 23 Jun 2005 15:28:46 +0000 Received: from ms5.netsolmail.com (IDENT:mirapoint@[216.168.230.178]) by omr1.netsolmail.com (8.12.10/8.12.10) with ESMTP id j5NFSeTj002893 for ; Thu, 23 Jun 2005 11:28:41 -0400 (EDT) Received: from rivatek.dnsalias.net (rrcs-67-52-40-201.west.biz.rr.com [67.52.40.201]) by ms5.netsolmail.com (Mirapoint Messaging Server MOS 3.2.2-GA) with ESMTP id DQN70112; Thu, 23 Jun 2005 11:28:39 -0400 (EDT) Received: by rivatek.dnsalias.net (Postfix, from userid 501) id 21EAE49B78; Thu, 23 Jun 2005 10:28:39 -0500 (CDT) To: ecos-discuss@ecos.sourceware.org From: Grant Edwards In-Reply-To: <200506231325.41733.sinany@beko.com.tr> References: <20050622182844.7476.qmail@web88210.mail.re2.yahoo.com> <200506231104.32693.sinany@beko.com.tr> <20050623090215.GF12265@lunn.ch> <200506231325.41733.sinany@beko.com.tr> Date: Thu, 23 Jun 2005 15:28:00 -0000 Message-Id: <20050623152839.21EAE49B78@rivatek.dnsalias.net> Subject: [ECOS] Re: ECOS - MIPS X-SW-Source: 2005-06/txt/msg00225.txt.bz2 In gmane.os.ecos.general, you wrote: > patterns means reusability of the design and architecture. if > u want your opearting system to fullfill future requests, i > must strongly suggest to use them.the things that eCos uses is > traditional C programming way of doing reusability and > maintainability. Right. > modern operating systems must modern software ideas and > architecture. You're free to write your own. eCos suits my needs quite nicely. > Pattern oriented architecture is not a new idea > but none of the embedded operating systems uses them. Firstly, there might be a reason for that. We're not stupid, you know. Secondly, I have no idea what you mean by "pattern oriented architecture" can you point to a description? The things that Google found were either describing ways to fail: Pattern oriented architecture - A trend that's found in systems created by architects who've recently read and digested books on architectural patterns and come to the conclusion that implementing patterns (such as front-controller, etc) is the key to a successful architecture. Rather than determining if common patterns are appropriate, and picking the most suitable one, all patterns that can be applied are done so, on top of one another, creating an entangled, schizophrenic system. or were marketing buzword-bullshit: A standards-based, pattern-oriented architecture that follows industry best-practices assures that the NEFS will fit right into your development environment. > Java classes are dynamically loaded. Java will be a future for > embedded systems. Many companies started to use java. it has > many benefits. If performance problems are solved, Java will > be a revolution for embedded systems. People have been saying that for 10 years. I stopped paying much attention 5 years ago. Java requires MASSIVE amounts of storage compared to eCos. > i am going to write an operating system with patterns and > reusable architecture. i will share it with you in the future > when i finish. OK. -- Grant Edwards grante Yow! I own seven-eighths at of all the artists in visi.com downtown Burbank! -- Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss