sockets vs browser.......
- Thread starter 00system
- Start date
HatIsBlack
Regular Member
- Sep 17, 2010
- 266
- 188
Browser:
You download everyting. Images,Javascript,Css files and everything else that is in the url. Upon that the page needs to be renderd, browser controls tend to be buggy and slow and you can't set proxys or headers as you want ..
In short. Advanced programs can't do what they want.
Sockets:
You control _everything_ that has with the connection to the server. You download what you want. You render what you want. and if someting is buggy you can correct it since it's your own code.
In short. You can do everything that requries a connection.
You download everyting. Images,Javascript,Css files and everything else that is in the url. Upon that the page needs to be renderd, browser controls tend to be buggy and slow and you can't set proxys or headers as you want ..
In short. Advanced programs can't do what they want.
Sockets:
You control _everything_ that has with the connection to the server. You download what you want. You render what you want. and if someting is buggy you can correct it since it's your own code.
In short. You can do everything that requries a connection.