[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[news.eclipse.technology.koi] Re: Case for SOAP
|
- From: Jan Joseph Kratky <kratky@xxxxxxxxxx>
- Date: Wed, 15 Jan 2003 15:20:07 -0500
- Newsgroups: eclipse.technology.koi
- Organization: IBM
Hi Allen:
How does the current XML-RPC module on the client recieve the web services
calls? Do you make use of the Tomcat App Server that ships with Eclipse for its
help system, or does your XML-RPC module actually act as its own mini-HTTP
server?
Thanks,
Jan Joseph Kratky
Allen Wirfs-Brock wrote:
> Our current thinking is that we will use the Apache Axis SOAP
> implementation. When we were implementing the RPC layers of the Koi
> prototype last spring/summer Axis was not yet far enough along to be usable
> and it didn't look like the predecessor Apache SOAP implementation was going
> to fit our needs. So, as an interim solution we just went with XML-RPC.
>
> We're looking for people who want to get involved with the SOAP work. If
> you are interest let me know.
>
> Allen Wirfs-Brock
> Koi project Lead
>
> "Ed Burnette" <ed.burnette@no.spam.sas.com> wrote in message
> news:atq2j9$u1a$1@rogue.oti.com...
> > Koi looks interesting, and I've read the FAQ about XML-RPC vs. Soap and
> the
> > Server-Side Plugin section. But... the FAQ says using XML-RPC "allowed
> > Apache time to develop a production quality SOAP implementation". Well, I
> > think there are a couple good SOAP implementations available now. I use
> JAXM
> > in a production environment and it works fine. I would argue that while
> > using XML-RPC is fine for a prototype, you should move immediately to
> using
> > SOAP Web services exclusively for maximum interoperability (in the first
> > public version if possible) and drop the XML-RPC support.
> >
> > You write you want to avoid focusing on the "intricacies of SOAP" but at
> the
> > simple level you're currently using I don't see how SOAP is significantly
> > harder or more complicated than XML-RPC. Just my opinion, but I think
> moving
> > now will better position you for the future (with security and routing and
> > other research coming to fruition in SOAP, not to mention broad industry
> > support) and the sooner you make the conversion then the less
> compatability
> > problems you'll have.
> >
> >
> >