[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: Thu, 16 Jan 2003 09:23:55 -0500
- Newsgroups: eclipse.technology.koi
- Organization: IBM
I guess that where I'm headed with this is that perhaps some sort of web server
that anyone could use might be a good thing to include as part of the base
Eclipse. That would make it a whole lot easier to write applications in which
the workbench acts as a "server". For example, if you were to move to AXIS,
wouldn't it be a whole lot easier to just use some sort of Tomcat plug-in in
order to integrate AXIS? (And if you were to change Web Services
implementations, oh boy). Another example: security is going to be a *huge*
issue with KOI. If there were a fully-functional Tomcat app server plug-in
available, it sure would be a lot easier to enable HTTPS.
So, I guess, to sum up, I am not sure the KOI subproject should be in the
business of writing its own "mini-HTTP-server", and that the availability of
some standard/open, but still reasonably lightweight, server implementation on
the workbench would be a good idea. Eclipse already has one of these -- the
Tomcat instance that serves up help pages. The org.eclipse.tomcat plug-in seems
to "hide"/"wrap" a lot of Tomcat, making it perhaps not as extensible as it
would need to be for the sorts of things I'm talking about (for example, I don't
see a server.xml file). And, perhaps the people responsible for Eclipse help
wouldn't want to expose that particular app-server plug-in, to avoid the danger
of someone disabling the existing help, but the bottom line is that some sort of
well-defined, standard app-server plug-in that could be shared seems like a good
thing.
Tim O'Connor wrote:
> jan:
>
> > or does your XML-RPC module actually act as its own mini-HTTP server?
>
> In short, yes. Apache XML-RPC provides a simple WebServer class that
> Koi launches when XML-RPC is used as the RPC protocol.
>
> to'c