Hi Samul
It is one thing to have a member authenticated to a specific group. And
another to have isolation of groups with identical names. For member
authentication within a group, the member needs to pass in a Certificate
object through Properties. Now, although Jxta supports it we have not
implemented code to support that. For group level isolation, please see
below.
Are the identically named groups expected to be in the same subnet?
If not, then as long as your router/switch does not support passing
multicast messages between groups, you should be able to retain
identically named groups.
If you do have groups within the same subnet, you can achieve isolation
by using different multicast address and port for each group.
Let us know if this works for you.
--shreedhar
Samul D wrote:
> Hi,
>
> I am trying to evaluate shoal clustering in my application and I am
> facing some problem, could you anyone help me in this regard?
>
> In our application we have provision of maintaining same group name
> in different installations, so there is always chance of one group
> member joining in another group. Because of this we are planning to
> maintain an unique ID in addition to group name. In this case, do we
> have an option or API to deny a non member joining a group? Also do we
> any other Unique way of identifying a group other than group name?
>
> Thanks in Advance,
> Samul
>
>
>