tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Carreira, Jason" <>
Subject RE: config diag, etc
Date Wed, 04 Aug 1999 14:25:43 GMT
> -----Original Message-----
> From: James Todd []
> i echo. well stated. i did not draw "protocols" supported but
> i kind of assumed when one was interacting with a jsp and/or
> servlet interface it was understood that it was over http and
> as such the client could be impelmented in any flavor. rmi is
> more java-centric but could possibly be wrapped with an orb
> (or the underling objects) to play in an open object request
> scenario. jndi is indeed a java play. are there other "service
> protocols" that should be considered?

Perhaps, since there is a general feeling that this config service not only
needs to be accessed by apps in other languages, but also needs to be
implementable in other languages, we should first work on a CORBA IDL for
the config API, then work out a reference implementation of the API in java.
To the reference impl we could add RMI and JNDI hooks that would be outside
the scope of the API (which would be the IDL) but put there to hook more
easily into java clients/tools... There could also be a separate API for
http/s clients/tools to interface with the config service that would also be
back-end-implementation independent, although I'm not sure how such can be

This would allow us to build the implementation without worries about Apache
standalone users not wanting to start up a JVM for the config service... it
could be implemented in C/C++ if necessary...

View raw message