my vote is against xml-rpc. why not turn the efforts into improving soap (and ksoap) as needed? to carl's comment, soap can be used as an XML/RPC over HTTP w/o the use of UDDI. and if leveraging web services, then use UDDI and WSDL, etc... ceo -----Original Message----- From: me-admin@enhydra.org [mailto:me-admin@enhydra.org]On Behalf Of Keith Bigelow Sent: Wednesday, October 10, 2001 4:16 PM To: me@enhydra.org Cc: kgabhart@objectsoln.com Subject: ME: RE: SV: RE: XML-RPC Sorry that I've delayed my notes back to the list. Given the public support of +1s and no -1s, it seems like a good idea to bring this project into the EnhydraME family. We'll be working with Kyle to get kXML-RPC, or kXPC or whatever Kyle calls it live as soon as we can, thanks, keith -----Original Message----- From: me-admin@enhydra.org [mailto:me-admin@enhydra.org]On Behalf Of Martin Husted Hartvig Sent: Monday, October 01, 2001 8:11 AM To: me@enhydra.org Subject: ME: SV: RE: XML-RPC Having make a dist. application running RMI on a Ericsson GPRS phone and seeing what that did do with the response times, I join in Kyle Gabhart and Carl Zetie and vote on +1. Keep it small and look after what you are using of bandwidth that is what I learned. Regards, Martin -----Oprindelig meddelelse----- Fra: me-admin@enhydra.org [mailto:me-admin@enhydra.org]På vegne af Zetie, Carl Sendt: 1. oktober 2001 16:32 Til: me@enhydra.org Emne: ME: RE: XML-RPC <non-technical person> My biggest concern with full SOAP functionality is less the bandwidth and more the latency. If one uses SOAP to its fullest extent, it implies potentially numerous round-trips to the UDDI registry, then to the service, then to negotiate the interface (of perhaps several available) and finally to actually invoke the service. That might be OK on a wireless LAN, but might well be unacceptably slow on a phone network (even 3G). When I raised this possible problem with A Large Vendor the response was, "in that situation you wouldn't use SOAP in full, you'd just hardcode the URL" - which sounds like an argument for XML-RPC to me. So... if the concern about latency above is valid, and XML-RPC can address that concern, I'd vote for +1. </non-technical person> _______________________________________________ ME mailing list ME@enhydra.org http://www.enhydra.org/mailman/listinfo.cgi/me _______________________________________________ ME mailing list ME@enhydra.org http://www.enhydra.org/mailman/listinfo.cgi/me _______________________________________________ ME mailing list ME@enhydra.org http://www.enhydra.org/mailman/listinfo.cgi/me |