Return-Path: Delivered-To: apmail-geronimo-dev-archive@www.apache.org Received: (qmail 50593 invoked from network); 5 May 2006 07:39:26 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 5 May 2006 07:39:26 -0000 Received: (qmail 1051 invoked by uid 500); 5 May 2006 07:39:22 -0000 Delivered-To: apmail-geronimo-dev-archive@geronimo.apache.org Received: (qmail 998 invoked by uid 500); 5 May 2006 07:39:22 -0000 Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: dev@geronimo.apache.org List-Id: Delivered-To: mailing list dev@geronimo.apache.org Received: (qmail 978 invoked by uid 99); 5 May 2006 07:39:22 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 05 May 2006 00:39:22 -0700 X-ASF-Spam-Status: No, hits=1.9 required=10.0 tests=DNS_FROM_RFC_ABUSE,DNS_FROM_RFC_POST,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: domain of andyp@bea.com designates 63.96.162.5 as permitted sender) Received: from [63.96.162.5] (HELO ussjmh01.bea.com) (63.96.162.5) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 05 May 2006 00:39:20 -0700 Received: from eagle.bea.com ([172.24.28.105]) by ussjmh01.bea.com (Switch-3.0.5/Switch-3.0.0) with ESMTP id k457cvBd014107; Fri, 5 May 2006 00:38:58 -0700 Message-Id: <6.2.5.6.2.20060505083822.02758de8@bea.com> X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6 Date: Fri, 05 May 2006 08:38:58 +0100 To: dev@geronimo.apache.org From: Andy Piper Subject: Re: Was: Clustering: Monitoring... - Now: Clustering: OpenEJB... Cc: dev@geronimo.apache.org In-Reply-To: <445AC88D.4070505@hanik.com> References: <4458D199.3010009@coredevelopers.net> <3B0B4762-F0D0-4018-9316-59F89C010980@visi.com> <4459B3E7.60405@coredevelopers.net> <3AA5E052-0EB3-424A-A20D-EA7F13DF0427@visi.com> <445A865E.1000307@coredevelopers.net> <445AC88D.4070505@hanik.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-PMX-Version: 4.7.0.111621, Antispam-Engine: 2.0.2.0, Antispam-Data: 2006.4.19.125107 X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N The weblogic thin-client works this way - clustering is built into the client using portable interceptors and the JDK ORB. andy At 04:37 AM 5/5/2006, Filip Hanik - Dev Lists wrote: >Jules Gosnell wrote: >>David Blevins wrote: >> >>> >>>On May 4, 2006, at 12:57 AM, Jules Gosnell wrote: >>> >>> >>>Sort of. Both your explanations involve smartening the java clients >>>on the other end of WS or CORBA to play nice. >> >>?? >> >>smart java stubs for RMI over OpenEJB-protocol (what is it called?) or IIOP. >> >>for WS, the load-balancer will do it. >> >>>The goal of those protocols is to interop in a language agnostic >>>fashion. WS are all stateless for EJB, so there is nothing to cluster anyway. >> >>stateless calls are still clustered - the load-balancing and >>failover considerations still exist - you just do not require >>session affinity (stickiness). If you are talking about server-side >>requirements, then I agree. >> >>>But for IIOP, would we simply not offer clustering to people >>>using CORBA to interop with clients in other languages or on other platforms? >> >>to tell the truth, these cases have escaped my radar - My CORBA >>knowledge is pretty thin and I have only really considered it in a >>java/java environment - I am sure that Kresten would be much better >>positioned to answer this question... I will CC this to him, in >>case he would like to pick it up... >corba is not far from RMI, and the corba implementation that you >use, create their own stubs, and those stubs can do the same stuff >as smart RMI stubs. I'm sure that corba could even do dynamic >proxies in some sort of sense, they werent able to when I used it a >long time ago, but if the technology has kept up, then yes, you >should be able to build in significant logic in the clients. > >Filip _______________________________________________________________________ Notice: This email message, together with any attachments, may contain information of BEA Systems, Inc., its subsidiaries and affiliated entities, that may be confidential, proprietary, copyrighted and/or legally privileged, and is intended solely for the use of the individual or entity named in this message. If you are not the intended recipient, and have received this message in error, please immediately return this by email and then delete it.