On Monday 06 February 2006 12:22, Philip Tellis wrote:
Sometime Today, DRR cobbled together some glyphs to say:
I expect an answer to my poblems...
ok, fine, here's the answer to your problems. Go ahead, download the source code of gaim, hack it to make it work with a proxy (not too
I hope you realize you are embarassing yourself. Gaim already has an option to use proxy servers ( socks 4/5 and http + authentication ).
About meebo - here's a technical reason why it's not 'as good' as a desktop app. Meebo is based on a pull model. ie, the web client keeps polling the server to find out if something has changed, and then pulls the data if it is. Your desktop app works in a push-pull model. The server can push data to the client when it has something, and the client can pull data from the server if it wants something.
Why is one better than the other? Polling in general is not good. There is too much CPU, application time and network overhead lost in checking for updates. There's also the issue of how often does one poll. If you poll too fast, you could overwhelm the server and network. If you poll too slowly, you lose the pseudo real time feel. With sufficient guess work and testing, you can settle on a reasonable window that's 'acceptable' if not perfect.
I don't see anything wrong from meebo's point of view. I'd thought of doing something similar in 2003 as a sample implementation of libyahoo2, but the aforementioned trust issues are what told me to spend my time elsewhere. If you're good enough, maybe you can take that forward.
Good explanation. But with Ajax there really isn't another way of implementing it.
It's fine to ask questions, but when you live on the cutting edge, you have to be prepared to maybe find the answer on your own.
A fine statement indeed.