HTTP wont solve your problems if you have connection issues, but it should be used for all communications.
Could you elaborate "connection issues"?
I don't have connection issues.
I have coding "issues". not really issues, but yeah....
I guess, I assumed if you cant send large amounts of data, then there is a connection issue. What sizes are you talking about?
I like HTTP because its a no brainer. ie: There are many HTTP libraries, and how can you not like sending data with one command?
**EDIT**
On a "debatable" topic. The only issue I have with HTTP is its name. "Hypertext Transfer Protocol". It somehow implies HTTP is only for HTML, and anything else is not well suited to HTTP.
Ive seen that one issue causing programmers to design there own protocol which is nothing more than re-inventing the wheel.
I was on a project where HTTP was not chosen for 3 reasons:
1) HTTP is not suited for XML (incorrect)
2) The HTTP package size is large. (incorrect)
3) HTTP is stateless (correct, but a stateless design handles broken connections)
Basically, a lot of code was written which didn't have to be written, which caused a lot a bugs, and made the entire system brittle. ie: A minor glitch in TCP caused components to stop working, which required them to go though an elaborate logon procedure.
It was all really stupid IMHO, and was a total head case to debug. All because HTTP has a slightly incorrect name.
Plus! on top of all of that, they somehow wanted a system where companies could write their own components in other languages, assuming they first implement a custom protocol, even though every language already has HTTP client/servers.
Crazy! But, that's what they did, and it wasn't long before the company was closed and moved off shore, and everyone was out of a job.
Soo, why HTTP? Its easy, portable, well documented and it works.