Sockets would be better and lighter weight

_________________
Lostboy

Cat, the other other white meat

Please read Posting Etiquette before posting

You can always try Google

HTTP is a protocol which run the socket where Socket is what transfer data from the two system. A socket is a sub-division of IP address.

_________________
puzzle

An important difference is that HTTP is supported both MIDP 1.0 and MIDP 2.0, while the sockets are optionally supported protocol is MIDP 2.0. You have the app much better chance to work with many phones, if you are using HTTP.

_________________
mothers day flowers delivered

HTTP is guaranteed to be supported by MIDP this is usually the best protocol choice due to portability. HTTP moves through firewalls basically since it usually operates over port 80. However, of the protocols discussed, HTTP incurs the most overhead, which may drive up the user's cost of using the application on the network.

_________________
Wypalls

hi
Not sure if this sounds like the right spot to post this particular because it kind of fits everywhere! hehe

Anyhow, we are designing a new bit of equipment which will deliver communications to the server. The actual question I have is whether or not we deliver the actual communications vie http to some PHP page or even make use of electrical sockets -- possibly using a php listening outlet. I am trying to find info on that way is the best way to proceed -- just about all I'm able to discover are a handful of electrical sockets lessons however these do not really answer the query as to that is best.

The issue we are looking forward to the the amount - the actual communications are extremely little Nine bytes normally however there will eventually be many of them. They chilly grow to Six thousand a minute. We don't wish to place a strain on the web host by getting all these communications and at the same time serving web pages to the customers. Additionally we're being charged a system charge with regard to bandwidth.

My personal thinking that the packages delivered upon Http could be bigger because of the header info? However has anybody obtained any kind of idea just how much larger? Can anybody think about any serious factors not to go with the socket strategy?

We're running a Light host on Cent Operating system.

_________________
tea kettles
Digital Photo Frame

Hi there,

I "socket" merely links two systems with each other, an IP address may be the
address of the device over an Internet protocol based system. Should you link Two systems
with each other using TCP, that's known as a TCP outlet, a outlet takes a interface
and an Ip to try to create a link.

A "protocol" is really a rigid set of guidelines with regard to sending specific kinds of
data with regard to set purposes. For example Internet protocol dependent video games utilized unique protocols
with regard to speed, AOL I'm utilizes it's personal bespoke process to create an instant
texting service, SMTP is really a protocol used for delivering emails. It's kind of
like a "language" designed for a particular purpose.

The protocols should only interfer having a firewall when the firewall is
possibly

A) Blocking the main harbour through getting used.
B) Sniffing the packages as well as making presumptions as well as presumptions,
leading to consequentions and making aspertions... along with other shuns that
firewalls have a habbit of doing.

But if you tell your own firewall to allow connects on a specific interface for
a specific software it will *not* give Two hoots about what has been
delivered forward and backward because it wouldn't be also able to comprehend
this! A firewall may analyze recognized protocols with regard to harmful signal, for example
HTTP, SMTP or POP3 but not your personal bespoke process.

TCP as well as UDP tend to be *low level* methods used by the actual network adapter to
transfer information more than Internet protocol dependent networks. And yes you're correct, UDP doesn't
contain fall short secure measures; like TCP.

But utilizing HTTP like a process inside your application could be absurd unless
you are making an internet server. It's undoubtedly simpler to make your *own*
process, believe me this really is *not* hard, I'm really creating a set of
courses for VB.NET at the moment which make designing your own protocol a
easy. Enter into Netlinx, AMX and Crestron then you'll understand
all about protocols, including how you can tear them away.

_________________
Futuristic Bike
Best sound card