🚀 go-pugleaf

Ok, got the book looking at the examples.

Question: the apps that are doing the listening are a bunch of web apps
jsp/servlets. Lets say I have 5 of them and they all need to listen on this
port. If I create a monitor class that uses a ServerSocket than I can only
have one of these web apps listening.

How about creating one monitor class that starts when the web server starts.
Then all my web apps register with this monitor class to receive commands.

1: should this monitor class be a servlet?
2: how can I get the monitor class to start when the server starts?
3: how can classes in other web applicatons register themselves with this
servlet?

Thanks for any help.

Alex


"Joi Ellis [TeamB]" <joi@aravox.com> wrote in message
news:3b98cc80_1@dnews...
> Alex Colic <alex.colic@pop-ware.com> wrote:
> > Hi,
>
> > Ok I am obviously doing something wrong. I picked the ServerSocket
class
> > because I do not know what host is going to send me commands, just the
port.
>
> > Any idea how I can have more than one class just listen to the same port
for
> > commands?
>
> You can't.  The general idea for this is to have a class that does nothing
> but listen, then spawns threads to handle incoming connections.  Once the
> child threads have their sockets, the parent goes back to listening for
> more connections.
>
> This is pretty much how inetd works on *nix.  There are examples of doing
this
> in Java in the O'Reilly 'Java Networking' book, among others.
>
> --
> Joi Ellis (TeamB)               http://www.teamb.com/
> No direct email, please.
> For best results, post on news server newsgroups.borland.com!
> Newsgroup Guidelines: http://www.borland.com/newsgroups/guide.html
> Only posts which violate the rules in guide.html are subject to
cancelation.