Return-Path: Mailing-List: contact tomcat-dev-help@jakarta.apache.org; run by ezmlm Delivered-To: mailing list tomcat-dev@jakarta.apache.org Received: (qmail 32306 invoked from network); 31 Jan 2000 22:21:22 -0000 Received: from mercury.sun.com (192.9.25.1) by 63.211.145.10 with SMTP; 31 Jan 2000 22:21:22 -0000 Received: from shorter.eng.sun.com ([129.144.251.35]) by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id OAA15915; Mon, 31 Jan 2000 14:21:19 -0800 (PST) Received: from tallest (tallest [129.144.251.237]) by shorter.eng.sun.com (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with SMTP id OAA26488; Mon, 31 Jan 2000 14:21:19 -0800 (PST) Date: Mon, 31 Jan 2000 14:21:19 -0800 (PST) From: "Anil K. Vijendran" X-Sender: akv@tallest To: new-httpd@apache.org cc: tomcat-dev@jakarta.apache.org, JServ Development Subject: Re: [Proposal] "Relayed" Apache API Project In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Mon, 31 Jan 2000 Costin.Manolache@eng.sun.com wrote: > Corba is a huge thing, IIOP is just a simple binary protocol. > Well, it's not simple - but that's because it support many complex types, > etc - for our purpose we can just use a subset of IIOP. Subsets are dangerous unless we can make sure we actually interoperate, which is possible. Least of all there is value in atleast writing the Tomcat side of the connector/adapter using the JavaIDL ORB in JDK (1.2). > Yes, we need a request forwarding and callback protocol - but instead of > defining an arbitrary encoding and arbitrary message format we can just > reuse CDR ( strings are sent as legth + bytes - like in AJP ), and we can > just use the message format of IIOP ( MsgType, magic, version, etc). We can use the GIOP message format, CDR encoding and add the *IOR* format. That would make it interoperable. For this, there's lots of places we can steal code from :-) -- Peace, Anil +<:-)