EnydraME Developers and Enthusiasts, I would like to take a few moments of your time and present a position in favor or a J2ME XML-RPC project. Although SOAP is powerful, flexible, and robust while still being relatively lightweight, "relatively lightweight" doesn't cut it in the embedded world. SOAP requries too much bandwidth and too much processing power when operating on micro devices. Certainly, it is possible to use a mobile or embedded device as a SOAP client (ksoap being an excellent example of such), but XML-RPC provides about half the functionality at a fraction of the cost. That may not sound like a very good deal, but SOAP is very much like the human brain -- its capabilities are endless, but most people use about 5% of that potential. What most people are doing with SOAP can easily be done via XML-RPC at a fraction of the cost in terms of memory and bandwidth! "But Kyle, bandwidth is becoming less of an issue and micro devices are becoming more powerful." True, but thanks to miniturization, we will continue to produce smaller devices with the same limitiations and memory constraints as larger devices. Also, more powerful micro devices are often overloaded with more features (color, sound, heavier background processes). Thus we find that micro devices suffer from the same axiom that desktop devices do: "What Intel giveth, Microsoft taketh away!" I'll get down off of my *soap* box now. (Sorry, I just had to throw that pun in there!) I encourage your feedback. My vote is a resounding: <H1>+1</H1> Thanks. Cordially, Kyle Gabhart Director of Java/EJB Division kgabhart@objectsoln.com Objective Solutions, Inc. http://www.objectsoln.com ___________________________ JUG Founder kyle@wsjug.org Web Services Java Users Group http://www.wsjug.org ___________________________ -----Original Message----- From: Keith Bigelow [mailto:keith.bigelow@lutris.com] Sent: Friday, September 28, 2001 12:21 PM To: me@enhydra.org Subject: New proposal to extend EnhydraME, need community feedback please - J2ME XML-RPC?? Hi all, We have ~70 developers now on the EnhydraME projects, and interest in contributing is increasing all the time. The latest proposed contribution is an XML-RPC implementation for EnhydraME (see http://www.xmlrpc.com/ for details, and see http://ksoap.enhydra.org for the contrasting approach). When the current chairs received the inquiry, we saw value in the additional implementation in having a slightly lighter-weight implementation with a less global goal than SOAP (there is of course some overlap in the benefits of an XML-RPC implementation and the existing kSOAP implementation), and also some drawbacks (potential confusion over 'when should I use kSOAP vs. kXML-RPC?'). After a brief discussion, we decided the best method of resolving if we should open this project up at http://me.enhydra.org was to ask the community [gee, what a novel idea, follow the Enhydra Community Process! <smile> http://mapper.enhydra.org/aboutEnhydra/gettingInvolved/ecp/index.html] So, in traditional open source form, we're asking you 70 silent developers out there to respond with: +1 = bring it on, choice is good, and we won't get in the silly religious battles about XMLRPC vs. SOAP that exist elsewhere 0 = I'm indifferent, could be good for others -1 = bad idea, keep this project tightly focused on the kSOAP implementation We'll allow voting until 10/05/01 (1 week from today), and we encourage you to respond!!!! thanks, keith |