Hi Antonio,

> - Extract the component into a separate JVM, and connect to it via
socket.

This is what I'd do, but I'd also write a client class to get access. I
suppose you could use RMI or something, but I'm not familiar with that.
Whatever you're comfortable with, I guess.

You could also spin off this class in it's own thread inside one of your
classloaders. That way it would shutdown and start up with the server
(or maybe that's a drawback...) and you wouldn't have to add the
overhead of another VM.

> - Extract the component into another context, and connect to it via HTTP.
> 

yuck.


This isn't for locking or something is it? I get the feeling you're
trying to use a class for storing or accessing something the way most
people use a database...

On Sun, 2003-06-15 at 08:21, Antonio Fiol Bonnín wrote:
> Hello,
> 
> This question is probably not specific to Tomcat, but a Tomcat-specific 
> answer could well suit my needs.
> 
> I have an application which I have split in several different contexts. 
> I have done so, to allow different kinds of access to the app, depending 
> on the web server the requests are coming from.
> 
> However, I need a common unique component that "ties" all the contexts 
> together.
> 
> There must be a *single* instance of this component, otherwise 
> inconsistencies or duplicate work might arise. OTOH, it must be 
> accessible from all the contexts.
> 
> Calls to this component are very simple (calls to void methods) but 
> moderately frequent.
> 
> I have thought of several possibilities:
> 
> - Extract the component into a separate JVM, and connect to it via socket.
> - Extract the component into another context, and connect to it via HTTP.
> --- I like none of those.
> 
> - Create the instance from the first context needing it, and making it 
> available to all of them.
> --- I like this best, but I have no idea of how to do that.
> 
> 
> Yours sincerely,
> 
> 
> Antonio Fiol
-- 
Mike Johnson <[EMAIL PROTECTED]>


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

Reply via email to