Prev: Not able to change baud rate
Next: Basic Shell concept
From: Bill Cunningham on 29 Mar 2010 17:28

"Ian Collins" <ian-news(a)hotmail.com> wrote in message
news:819s60F6jlU8(a)mid.individual.net...

> A connection is a connection. It's what you do with it that matters.
>
> By the way, your clock is an hour fast.

Well I guess there are INET and STREAM sockets atleast anyway. Since I
want to experiment with smtp and pop3 I guess I've have to look up their
port numbers again and see if the run on TCP or UDP since I can't remember.
This thing I'm reading talks about inter-process communication which brings
pipes and child processes to mind for me. Socket must be used within an OS!
But that must be the STREAM and not INET sockets. The way the standard reads
socket.h must have all I need for client and server side. Client is all I'm
focusing on.

Bill


From: Rick Jones on 29 Mar 2010 16:42
Bill Cunningham <nospam(a)nspam.invalid> wrote:

> "Ian Collins" <ian-news(a)hotmail.com> wrote in message
> news:819s60F6jlU8(a)mid.individual.net...

> > A connection is a connection. It's what you do with it that matters.
> >
> > By the way, your clock is an hour fast.

> Well I guess there are INET and STREAM sockets atleast
> anyway. Since I want to experiment with smtp and pop3 I guess I've
> have to look up their port numbers again and see if the run on TCP
> or UDP since I can't remember.

If you were using getaddrinfo(), or getservbyname() your code would be
passing-in the service name to be resolved to a port number and then
you would not need to remember.

However, if you do wish to experiment with SMTP and POP then it would
indeed be goodness to look-over their specs.

rick jones
--
Process shall set you free from the need for rational thought.
these opinions are mine, all mine; HP might not want them anyway... :)
feel free to post, OR email to rick.jones2 in hp.com but NOT BOTH...
From: Rick Jones on 29 Mar 2010 16:44
Bill Cunningham <nospam(a)nspam.invalid> wrote:
> Well I guess there are INET and STREAM sockets atleast anyway.

There are the INET and Unix address families (AF_INET, AF_UNIX) and
then there are the STREAM and DGRAM style sockets (SOCK_STREAM,
SOCK_DGRAM). The former determine the type of addressing you use, and
so what you can reach from where. The latter determine the
characteristics of the data you send/receive over the socket.

rick jones
--
Wisdom Teeth are impacted, people are affected by the effects of events.
these opinions are mine, all mine; HP might not want them anyway... :)
feel free to post, OR email to rick.jones2 in hp.com but NOT BOTH...
From: Rick Jones on 29 Mar 2010 17:23
Rick Jones <rick.jones2(a)hp.com> wrote:
> Bill Cunningham <nospam(a)nspam.invalid> wrote:
> > Well I guess there are INET and STREAM sockets atleast anyway.

> There are the INET and Unix address families (AF_INET, AF_UNIX) and
> then there are the STREAM and DGRAM style sockets (SOCK_STREAM,
> SOCK_DGRAM). The former determine the type of addressing you use, and
> so what you can reach from where. The latter determine the
> characteristics of the data you send/receive over the socket.

That would be better put as "The latter determine the send/receive
semantics of the socket. For example a SOCK_STREAM socket will
present 'byte stream' sematics where message boundaries are up to the
application. SOCK_DGRAM will present 'message' semantics where
message boundaries are preserved by the transport."

rick jones
--
I don't interest myself in "why." I think more often in terms of
"when," sometimes "where;" always "how much." - Joubert
these opinions are mine, all mine; HP might not want them anyway... :)
feel free to post, OR email to rick.jones2 in hp.com but NOT BOTH...
From: Bill Cunningham on 30 Mar 2010 14:27

"Rick Jones" <rick.jones2(a)hp.com> wrote in message
news:hor5nk$hr1$2(a)usenet01.boi.hp.com...

> That would be better put as "The latter determine the send/receive
> semantics of the socket. For example a SOCK_STREAM socket will
> present 'byte stream' sematics where message boundaries are up to the
> application. SOCK_DGRAM will present 'message' semantics where
> message boundaries are preserved by the transport."

Now would I also need that header called inet.h or something like that
for IP information? Posix sure seems easier to me than regular old standard
C. Not quiute sure why though.

Bill


First  |  Prev  |  Next  |  Last
Pages: 1 2 3 4
Prev: Not able to change baud rate
Next: Basic Shell concept