Posted by Bruno Biancucci on November 22, 2011 at 21:16:53:
In Reply to: Comet THROUGH the Internet posted by steve auerbach on November 15, 2011 at 11:29:02:
Without knowing the details, here's my take on it (and in some cases only take up one Comet license per user)
1) Make one location the primary server, the other two locations could use Remote Desktop and connect to the server. RDP sessions only transmit screen updates, so little bandwidth required and the processing takes place at the server. Result it very fast comet sessions. Drawback is that it the primary location goes down, all three go down. If this works, consider installing a second internet connection with fail over (via a dns service like no-ip).
2) See if a VPN solution would fit. Then setup shared drives at three locations, adjust comet configuration. Might work, but accessing data from remote locations may not be the quickest. Ok for simple single inquires, but not for processing large files.
3) If the data would allow for it, think about doing data transfers between locations. If the data doesn't have to be real time, you could setup some kind of data sync (via transaction files?) to update two other locations every few minutes.
On a side note per Barbara's comment about static IP's. Does this mean that you can't use domain names in place of static IP addresses in comet.ini? Personally, I've never tried it, but one would have assumed that when ever you can insert a hard IP address, you would be able to replace that with a domain name (ie. mysite.com instead of 4.2.2.1).
Each file can be a maximum of 1MB in length Uploaded files will be purged from the server on a regular basis.