It depends on how many collisions occur. Name collisions can occur at
any time while running your application, so even if the name is
registered successfully at first, it's still possible that 30 minutes
later, somebody could connect a new hub with a service name that
conflicts with you, and you'll need to handle that situation.
Interesting. I'm confused. I thought only the latest app that
attempted to
register would get the collision, and then it should append a count to
the
end of the name and try again.
If an app successfully registers a service, then gets a collision 30
minutes
later, what is it supposed to do? Can't it ignore it?
You can ignore it if you want, but by the time you get a name collision
callback, your service is de-registered. So if you want to stay
registered after a name conflict, you'll need to choose a new name and
re-register.
If both apps get notified of the collision, who has the service at that
point? That is, if someone does a resolve, whose address will they get?
Only one application will get notified of a collision. Under normal
operation, the originally registered service will be able to keep its
name, and the new service attempting to register will get a name
conflict message, but in the case of someone joining two previously
disjoint ethernet networks together, there is no old or new service.
In that scenario, both applications successfully registered the service
name at some point in the past, and now when two networks are joined, a
name conflict occurs, and one of the applications at random will get a
name conflict message.
If you resolve a service at the time that two machines are using the
same name, you'll probably get responses from both machines, however,
at that point, the machines will notice the conflict and one of them
will get a name conflict message.
Keep in mind that the above mentioned scenario about joining networks
is extremely rare, so you shouldn't be worrying about it. Just know
that name collisions can occur at any time while your service is
registered, so be prepared.
-Marc
_______________________________________________
rendezvous mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/rendezvous
Do not post admin requests to the list. They will be ignored.
