Frequently Asked Questions
I get the following log message when running AmbientTalk under Windows: WARN at.network - Multicast Listener for communication bus: could not create socket to master:error setting options
For service discovery, AmbientTalk makes use of IP multicasting. AmbientTalk broadcasts messages to IP 244.0.0.1 on port 4446. Make sure your firewall does not block this port.
On Windows 7, multicasting on 220.127.116.11 seems to be disabled by default. The following should fix this issue: http://support.microsoft.com/kb/239924
Two AmbientTalk VMs do not seem to discover one another
iat.bat fails to launch
Note to windows users: iat.bat has been reported not to work when the AT_HOME directory contains spaces, so consider placing your AmbientTalk distribution in a directory that does not contain spaces. (This will be fixed in v2.19)
Is it possible that the same object gets discovered twice by means of
Yes, this is possible. If two AmbientTalk VMs disconnect and then later reconnect, they will again exchange their list of required and provided (exported) objects. This could lead to the same exported object being discovered twice. Applications should thus remove duplicates themselves, if this is required.
How do I load AmbientTalk namespaces / source files dynamically?
Cf. this mail.