BorlandTalk.com Forum Index BorlandTalk.com
Borland discussion newsgroups
 
Archives   FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

Message sending

 
Post new topic   Reply to topic    BorlandTalk.com Forum Index -> Delphi Internet Winsock
View previous topic :: View next topic  
Author Message
Richard Bibby
Guest





PostPosted: Fri Sep 29, 2006 1:51 am    Post subject: Message sending Reply with quote



Hej,

I have introduced a messaging system where my application can send me
information about exceptions etc. When I say me I mean our web server in
the office.

I want to keep overheads low for the application, so currently I am using
UDP on port 60. The sending of the message occurs in a seperate thread. It
works!

However I am not sure what protocol should I use. UDP or HTTP?

What port should I use?

However I have discovered that many networks do not let traffic out on UDP
port 60 so the messages never arrive.

So should I use HTTP on port 80?

/Richard
Back to top
Martin James
Guest





PostPosted: Fri Sep 29, 2006 8:11 am    Post subject: Re: Message sending Reply with quote



Quote:

However I have discovered that many networks do not let traffic out on UDP
port 60 so the messages never arrive.

Yes - many routers/firewalls/antiVirus can cause problems.

Quote:
So should I use HTTP on port 80?

That is my favorite - nearly always works.

Rgds,
Martin
Back to top
Jamie Dale
Guest





PostPosted: Sat Sep 30, 2006 4:18 am    Post subject: Re: Message sending Reply with quote



Why not use TCP?


"Richard Bibby" <richardjbibby (AT) hotmail (DOT) com> wrote in message
news:451c35ef (AT) newsgroups (DOT) borland.com...
Quote:
Hej,

I have introduced a messaging system where my application can send me
information about exceptions etc. When I say me I mean our web server in
the office.

I want to keep overheads low for the application, so currently I am using
UDP on port 60. The sending of the message occurs in a seperate thread. It
works!

However I am not sure what protocol should I use. UDP or HTTP?

What port should I use?

However I have discovered that many networks do not let traffic out on UDP
port 60 so the messages never arrive.

So should I use HTTP on port 80?

/Richard
Back to top
Richard Bibby
Guest





PostPosted: Sat Sep 30, 2006 5:34 pm    Post subject: Re: Message sending Reply with quote

can you explain a bit more?
"Jamie Dale" <j.dale (AT) turboz (DOT) net> skrev i meddelandet
news:451da9ad (AT) newsgroups (DOT) borland.com...
Quote:
Why not use TCP?


"Richard Bibby" <richardjbibby (AT) hotmail (DOT) com> wrote in message
news:451c35ef (AT) newsgroups (DOT) borland.com...
Hej,

I have introduced a messaging system where my application can send me
information about exceptions etc. When I say me I mean our web server in
the office.

I want to keep overheads low for the application, so currently I am using
UDP on port 60. The sending of the message occurs in a seperate thread.
It works!

However I am not sure what protocol should I use. UDP or HTTP?

What port should I use?

However I have discovered that many networks do not let traffic out on
UDP port 60 so the messages never arrive.

So should I use HTTP on port 80?

/Richard


Back to top
theo
Guest





PostPosted: Sat Sep 30, 2006 6:12 pm    Post subject: Re: Message sending Reply with quote

http://en.wikipedia.org/wiki/Internet_protocol_suite
Back to top
Jamie Dale
Guest





PostPosted: Sun Oct 01, 2006 1:55 am    Post subject: Re: Message sending Reply with quote

Transmission Control Protocol.
It is basically used for direct connections to and from a TCP server. TCP
also guarantees that each data packet will reach it's destination whereas
UDP does not.

UDP is good for broadcasting data - IE realmedia, sound etc, but is not
generally good for control communications etc.

For what you are building, it sounds like TCP is much more what you need to
be using. UDP is kind of like analogue radio. It is broadcasted, but
receiving it can be somewhat hard.

TCP is similar to digital/morse code. You receive it because the receiver
differentiates between 0's and 1's making errors or confusion extremely
unlikely.

TCP is also a slower protocol. It's time and resource consuming because of
it's complexity and processing requirements. UDP on the other hand doesn't
need a lot of resources as it basically just broadcasts without caring about
the end result.

I don't know what components you are using for your current UDP, but you
should look into Indy sockets or ICS (I think it's called). Indy is very
good but can be rather hard to get installed at the moment because the
latest version is also the live version - meaning that the team work on the
very same files downloaded from the server.

Remy would probably have a much better and precise explanation than me....

Jamie.


"Richard Bibby" <richardjbibby (AT) hotmail (DOT) com> wrote in message
news:451e6467$1 (AT) newsgroups (DOT) borland.com...
Quote:
can you explain a bit more?
"Jamie Dale" <j.dale (AT) turboz (DOT) net> skrev i meddelandet
news:451da9ad (AT) newsgroups (DOT) borland.com...
Why not use TCP?


"Richard Bibby" <richardjbibby (AT) hotmail (DOT) com> wrote in message
news:451c35ef (AT) newsgroups (DOT) borland.com...
Hej,

I have introduced a messaging system where my application can send me
information about exceptions etc. When I say me I mean our web server
in the office.

I want to keep overheads low for the application, so currently I am
using UDP on port 60. The sending of the message occurs in a seperate
thread. It works!

However I am not sure what protocol should I use. UDP or HTTP?

What port should I use?

However I have discovered that many networks do not let traffic out on
UDP port 60 so the messages never arrive.

So should I use HTTP on port 80?

/Richard




Back to top
Display posts from previous:   
Post new topic   Reply to topic    BorlandTalk.com Forum Index -> Delphi Internet Winsock All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum


Powered by phpBB © 2001, 2006 phpBB Group
SEO toolkit © 2004-2006 webmedic.