Re: [Q] CoreFoundation functions or Cocoa classes to make a server socket?
Re: [Q] CoreFoundation functions or Cocoa classes to make a server socket?
- Subject: Re: [Q] CoreFoundation functions or Cocoa classes to make a server socket?
- From: Jens Alfke <email@hidden>
- Date: Thu, 29 Jan 2009 11:34:41 -0800
On Jan 29, 2009, at 10:22 AM, Scott Ribe wrote:
If so, you could use your current pair of streams. Whenever the
client reads
a message from its NSInputStream, that message could be either the
response
to its last request, or a notification from the server--you'd just
have to
structure your messages such there's info in the header to
distinguish the
types of messages.
That's what the BLIP protocol I mentioned does. It's quite
lightweight; better to use it than to re-invent the wheel again.
(In fact, BLIP is itself sort of a re-invention of the earlier BEEP
protocol. In my defense, I initially used BEEP in my project, only to
give up after the one available implementation proved too buggy and
difficult to use in Cocoa apps. BLIP is much simpler but uses many of
the same ideas.)
—Jens
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Macnetworkprog mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden