Filip Hanik - Dev Lists wrote:
The biggest issue I have is that I keep getting
memberAdded/memberDisappeared events from the same member. I've made a
small test app (based on the example on the Tribes introduction page)
that I run on a client PC and a similar implementation that I start
from a ServletContextListener. The client app creates a group, starts
it, sends a message and then quits. I get the memberAdded event, then
the message, and then a memberGone, memberAdded,memberGone, etc. until
the client has died.
what is your config? could be a simple mistake.
There is no config, I basically tried the code that is in the 'introduction' page, which seems to be the only piece of documentation, and it doesn't mention anything about configuration. Also, I'm not running this on TC6 but on a TC5.5 server (I just added the apache-tribes jar to the lib directory of my webapp)

Can you tell me how I should configure this ? I'll have a look around the source in the mean time to see if I can figure this out myself.
Another issue is that there seems to be no way to define a group. If I
create a GroupChannel for use by application A, and in the same subnet
I create a GroupChannel for application B, application A will receive
messages for app B and vice versa, app A will see members from app B
join the group, etc.
Is it possible to create a group that's only for use within one
application ?
groups are divided up by the multicasting address/port if you are using
multicasting. furthermore, you can set the "domain" for each member, and
then have your application filter out based on that.
Is every application a member or is there one member for every host ? (can I e.g. set the 'domain' for app A to "com.ourcompany.productA" and the 'domain' for appB to something different and then filter on it or is the 'domain' setting per-host ?)

Tom

---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to