Return-Path: Delivered-To: apmail-jakarta-avalon-dev-archive@apache.org Received: (qmail 68625 invoked from network); 22 Nov 2002 20:31:36 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 22 Nov 2002 20:31:36 -0000 Received: (qmail 15820 invoked by uid 97); 22 Nov 2002 20:32:39 -0000 Delivered-To: qmlist-jakarta-archive-avalon-dev@jakarta.apache.org Received: (qmail 15804 invoked by uid 97); 22 Nov 2002 20:32:38 -0000 Mailing-List: contact avalon-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Avalon Developers List" Reply-To: "Avalon Developers List" Delivered-To: mailing list avalon-dev@jakarta.apache.org Received: (qmail 15787 invoked by uid 98); 22 Nov 2002 20:32:38 -0000 X-Antivirus: nagoya (v4218 created Aug 14 2002) From: "Noel J. Bergman" To: "Avalon Developers List" Subject: RE: Tiered Container Hierarchy Date: Fri, 22 Nov 2002 15:32:14 -0500 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) In-Reply-To: <3DDDAD89.4020202@apache.org> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Berin: > 1) Micro Container--a Tweety like container that can operate in J2ME. > It requires that only threadsafe components be used because it is > unlikely that multithreading will be used in that environment. As possibly one of the few people around here actually using J2ME (and a book on the subject in my lap), my only amendment here is that multi-threading does need to be permitted, just not required. It is optional in J2ME CDC, and supported in J2ME CLDC. As for the plan by which these containers arrive, I think that Stephen McConnell and Peter Donald have each posted ideas that could be woven into a community roadmap upon which to start the journey. PaulH: > Be ready for other containers [by] other teams (Turbine). And they'll benefit, too, from the development of a true framework for containers. They will be able to reuse the code and patterns developed for building the container tier. --- Noel -- To unsubscribe, e-mail: For additional commands, e-mail: