On Thursday, June 5, 2003, at 10:05 AM, Johan Sj�berg wrote:
AltRMI would work in that case. What would be *really* cool is a RemotingServiceManager or such that you could use in a client container, that would pass all lookups over AltRMI (or such) to an external container :)

Yes, that would be great. Have some AltRMI developer ever thought of such a ServiceManager? I must think about that... it can't be too hard to make one.

I've thought about it and I believe Paul Hammant has thought about it some too


It will probably be released here at Avalon at some point. The main thing that is missing is documentation. I can envision an API-release and then separate releases of the different implementations.

OK. I noticed that documentation was missing, but the code itself is very easy to understand. What kind of docs except API are needed for a release? I could perhaps (fingers crossed) help a little with that. I also noted (or missed something trivial) that it wasn't possible to configure AJP listeners for Jetty, but also that it would be a very small addition to the conf and init method to add that. Wasn't there a discussion earlier on this list about supporting Jetty's config file? Did anything happen there? I need that so I will have to add it somehow.

API docs.. simple regular documentation (its a thin wrapper, so not too much).


yes there was a thread about supporting the full breadth of Jetty's native configuration, I believe one of the Leo's posted some pseudo-code here a few weeks back on how that could be done. it should be a pretty simple patch.
-pete


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to