HP3000-L Archives

June 1997, Week 4

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Jeff Boehlert <[log in to unmask]>
Reply To:
Jeff Boehlert <[log in to unmask]>
Date:
Tue, 24 Jun 1997 21:48:29 GMT
Content-Type:
text/plain
Parts/Attachments:
text/plain (38 lines)
Sockets Implementation

Hello, I am a rookie faced with having to do a sockets implementation for
a project and I have come across a couple of varying philosophies on how
to implement the message exchange protocol for this. My needs are to be
able to transfer ASCII data messages (no binary data required). The
messages have a known terminating character (x07).  I am soliciting some
opinions on the correct/feasible approach: Thank you.



Philosophy 1
The sender is obligated to send a message length (ala a short integer)
followed by the message content. The receiver will then use the given
length to continue a receive loop until the entire message has been
received.


Philosophy  2
The sender sends out a stream of data with a known terminating character
and the receiver must continue to receive data until the terminator has
been received.

Other philosophies ???
???

      _  __________________________________________  _
     / )| Jeff Boehlert        [log in to unmask]   |( \
    / / |             Why run 26.2 ?               | \ \
  _( (_ |      Because it hurts so good !!         | _) )_
 (((\ \>|_/->__________________________________<-\_|</ /)))
 (\\\\ \_/ /    o      New York City      o     \ \_/ ////)
  \       /    < \      Marine Corp      < \     \       /
   \    _/    _/\        Portland       _/\       \_    /
   /   /       /          Big Sur        /          \   \
  /___/  ===============  Seattle  ===============   \___\
            Next stop - San Francisco July 1997

ATOM RSS1 RSS2