#2 Chat function across Instances

[Ronald Wertlen]

Issue:

there are several /live/ awareNet Instances. It must be possible for the presence and chat services to function across the instances transparently, so that to the user it seems that there is only one awareNet. This issue is related to the "Batch updateing" issue which also spans instances.

Functional Spec:
- I can see who is online in the entire awareNet and can chat with these people.
- awareNet Linking for chat purposes must be handled by an administrator. It is not possible, simply to download awareNet and to expand the network on your own. Basically if you install your own instance, it creates a new awareNet /island/, which is not connected to the main awareNet.

Non-Functional Spec:
- Presence and chat information is handled as quickly as possible, keeping in mind the latency to remote systems. Since the internet connection to remote systems can be very bad (up to 30 seconds for round trip, including processing), the update period need not be much shorter than 30 seconds for chats across instances. Obviously on local chats it makes sense to update the chat more frequently as is currently the case.
- Update checking for chat information should not impact significantly on the

[Ronald Wertlen]

- Update checking for chat information should not impact significantly on
the bandwidth use of the system as a whole, as Internet bandwidth and traffic is a very valuable resource in the remote installation. (count on 1GB per month, for all Internet use)

[Ronald Wertlen]

this is becoming more important as we face the likelihood of several cooperating instances...