Return-Path: Delivered-To: apmail-jakarta-avalon-dev-archive@apache.org Received: (qmail 63362 invoked from network); 7 Aug 2002 11:24:48 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 7 Aug 2002 11:24:48 -0000 Received: (qmail 11925 invoked by uid 97); 7 Aug 2002 11:25:07 -0000 Delivered-To: qmlist-jakarta-archive-avalon-dev@jakarta.apache.org Received: (qmail 11907 invoked by uid 97); 7 Aug 2002 11:25:06 -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 11895 invoked by uid 98); 7 Aug 2002 11:25:06 -0000 X-Antivirus: nagoya (v4198 created Apr 24 2002) Subject: Re: where I'm going with avalon From: Leo Simons To: Avalon Developers List In-Reply-To: <200208070706.49904.proyal@apache.org> References: <1028713292.1695.57.camel@test.multimia.multimia.com> <200208070643.51795.proyal@apache.org> <1028717307.1694.87.camel@test.multimia.multimia.com> <200208070706.49904.proyal@apache.org> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.5 Date: 07 Aug 2002 13:20:50 +0200 Message-Id: <1028719250.1694.111.camel@test.multimia.multimia.com> Mime-Version: 1.0 X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N > > Basically, I have a component in Merlin (well, I will have) that > > currently does: > > > > socket = cm.lookup("socket.to.component.in.phoenix"); > > // ... > > result = socket.createCall( myData ).execute(); > > > > Where I would like it to do: > > > > comp = cm.lookup("component.in.phoenix"); > > result = comp.myDataMethod(); > > AltRMI :) It has some trickery for same-JVM-different-classloaders that's > quicker than sockets (right paul?) it does (says so on the website). How far along is AltRMI? I've tried to follow the discussions on and off but the discussion generally is a bit difficult for me to follow. http://jakarta.apache.org/avalon/excalibur/altrmi needs some simple docs for people with my use case and little knowledge about remoting.... ...I figure I need to do this: for my component.in.phoenix, add AltRMI into my .sar, but then, how do I get to > compAccessor = cm.lookup("component.in.phoenix.accessor"); > > comp = compAccessor.getComponent(); > comp.doStuff(); > compAccessor.release( comp ); for the client? Also it seems it would be even cooler to have an AltRMIComponentManager so it is truly transparant on the client that I use AltRMI..... cheers, Leo -- To unsubscribe, e-mail: For additional commands, e-mail: