Is there a way to have more than one socket connection be made to the same
"accept" service?
For client connections, it appears that a session id plays a role in routing
so the same user can
connect multiple times. Is this true for server component connections? I
have a service defined
in the configuration:
<service id="alerter">
<accept>
<ip/>
<port>7000</port>
<secret>test</secret>
</accept>
</service>
When I try connect on two separate threads one of the handshakes times out
waiting for the <handshake/>
response (I set it up to 30 seconds), and one is always successful.
I have a server component that sends messages, often the same message to a
number of
of users and would like to have multiple threads to send these concurrently.
Since I have a
limited number of these, I have done a poor man's version as:
<service id="alerter0">
<accept>
<ip/>
<port>7000</port>
<secret>test</secret>
</accept>
</service>
......
<service id="alerterN-1">
<accept>
<ip/>
<port>7000 + ( N-1)</port>
<secret>test</secret>
</accept>
</service>
I was just wondering if there was a simpler way.
Thanks,
Bill
_______________________________________________
jdev mailing list
[EMAIL PROTECTED]
http://mailman.jabber.org/listinfo/jdev
