Forums » Bugs
Well two connections are usually better then one in most cases and would allow better diagnostics....
It creates more problems with firewall traversal and the like, and really has no benefit.
And Your connection would be ,,,, plugged into the back of the server? :P
I'm effectively on-net to the server via my home cable modem, because our colo has a GigE connection to the local cable network (among others).
A mission cache might help a lot along with a cache of roids - Its not like I have ever really been short on drive space since 1980......
There's a whole balance to be struck over making data quickly accessible (cached) vs dynamic and quick to update (streamed). Yes, we'll basically cache the "heavy" data, like mission descriptions and the like, while continue to push across the more lightweight specifics that could be more dynamic.
In the case of asteroids, we've considered caching sectors. We can also use the client to computationally generate the sectors using the same procedural algorithms as the server, basically meaning we don't have to cache anything (just send a hash). All options we're considering. But.. sector data isn't really the topic here.
It creates more problems with firewall traversal and the like, and really has no benefit.
And Your connection would be ,,,, plugged into the back of the server? :P
I'm effectively on-net to the server via my home cable modem, because our colo has a GigE connection to the local cable network (among others).
A mission cache might help a lot along with a cache of roids - Its not like I have ever really been short on drive space since 1980......
There's a whole balance to be struck over making data quickly accessible (cached) vs dynamic and quick to update (streamed). Yes, we'll basically cache the "heavy" data, like mission descriptions and the like, while continue to push across the more lightweight specifics that could be more dynamic.
In the case of asteroids, we've considered caching sectors. We can also use the client to computationally generate the sectors using the same procedural algorithms as the server, basically meaning we don't have to cache anything (just send a hash). All options we're considering. But.. sector data isn't really the topic here.
A port 80 tcp connection is usually allowed on most firewalls. I do suppose coordinating 2 connects on a dial up might cause a few unwanted hiccups....all moot points tho.
Hehehe... I am 2000 miles away and still manage a 100 ping. In this case tho I suspect the actual bandwidth is what matters as you are shoveling mass data out to us at every log in. It doesnt take much of a bottle neck out in the "cloud" to really drag things to a crawl. Not exactly your fault but you will get blamed for it in any case...... Such is the life of bein the man...enjoy ...
Hehehe... I am 2000 miles away and still manage a 100 ping. In this case tho I suspect the actual bandwidth is what matters as you are shoveling mass data out to us at every log in. It doesnt take much of a bottle neck out in the "cloud" to really drag things to a crawl. Not exactly your fault but you will get blamed for it in any case...... Such is the life of bein the man...enjoy ...