Hmm... yeah, I guess your right :) D'oh! I made the onconscious assumption that the slave would know about itself, but if that were true there wouldn't be any reason to do any of this, it could just send that information to the master straight away. Sorry, I missed the obvious :)
-- Frank W. Zammetti Founder and Chief Software Architect Omnytex Technologies http://www.omnytex.com AIM: fzammetti Yahoo: fzammetti MSN: [EMAIL PROTECTED] Java Web Parts - http://javawebparts.sourceforge.net Supplying the wheel, so you don't have to reinvent it! On Thu, March 16, 2006 4:06 pm, Leon Rosenberg said: > On 3/16/06, Frank W. Zammetti <[EMAIL PROTECTED]> wrote: >> Ok, here's another possibility... >> >> From the plug-in, launch a daemon thread (daemon just in case the server >> has to go down before the thread is done, in which case it won't block >> the >> shutdown). Have the thread sleep for some amount of time, 30 seconds >> maybe, however long on average it takes your app to start up. >> >> Then, the thread fires off a request to some known URL within your app. >> Just a simple GET using Commons HTTPClient sort of thing. Have that >> request execute an Action. Within the Action you can get all the info >> you >> need, so construct the URI and send it back to the thread. > > Aehm... :-) > If you would know the url you don't need the thread anymore because > the url contains the protocol, the host, the port and the path. It's > everything he needs :-) > > regards > Leon > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
