FROM : Michael Gardner
DATE : Sat May 10 21:35:05 2008
I've used SmallSockets (http://smallsockets.sourceforge.net/) in a
small project, with good results. It doesn't do run loop events, but
in my opinion it's better to just use threads with blocking I/O anyway.
-Michael
On May 10, 2008, at 2:11 PM, Jens Alfke wrote:
>
> On 10 May '08, at 11:59 AM, Wade Tregaskis wrote:
>
>> I haven't used it directly, but I did notice when looking at it
>> that it seems to rely on you polling it... that's terrible, given
>> you can setup a socket as a runloop source very easily and it
>> operates very efficiently.
>
> By Jove, you're right! From BTLSocketManager:
>
> //! \brief Updates the sockets.
> //!
> //! This method should be called often. Managed sockets will not
> recieve data or
> //! finish pending connections until this method is called. NSTimer
> can be used
> //! to call this method on a regular basis.
>
> - (void)select
>
> That is just absurd. It might have been excusable ten years ago in
> the classic OS, when threading and asynchrony were so difficult, but
> as you point out, you pretty much have to go out of your way to be
> this badly-behaved on Mac OS X.
>
> Let us never speak of it again :-/
>
> Anyone got a good socket framework to recommend? (I realize it's not
> that hard to roll your own with NSStreams, as shown in CocoaSockets,
> but a framework with a few more bells & whistles would be nice.)
>
> —Jens_______________________________________________
>
> Cocoa-dev mailing list (<email_removed>)
>
> Please do not post admin requests or moderator comments to the list.
> Contact the moderators at cocoa-dev-admins(at)lists.apple.com
>
> Help/Unsubscribe/Update your Subscription:
> http://lists.apple.com/mailman/options/cocoa-dev/<email_removed>
>
> This email sent to <email_removed>
DATE : Sat May 10 21:35:05 2008
I've used SmallSockets (http://smallsockets.sourceforge.net/) in a
small project, with good results. It doesn't do run loop events, but
in my opinion it's better to just use threads with blocking I/O anyway.
-Michael
On May 10, 2008, at 2:11 PM, Jens Alfke wrote:
>
> On 10 May '08, at 11:59 AM, Wade Tregaskis wrote:
>
>> I haven't used it directly, but I did notice when looking at it
>> that it seems to rely on you polling it... that's terrible, given
>> you can setup a socket as a runloop source very easily and it
>> operates very efficiently.
>
> By Jove, you're right! From BTLSocketManager:
>
> //! \brief Updates the sockets.
> //!
> //! This method should be called often. Managed sockets will not
> recieve data or
> //! finish pending connections until this method is called. NSTimer
> can be used
> //! to call this method on a regular basis.
>
> - (void)select
>
> That is just absurd. It might have been excusable ten years ago in
> the classic OS, when threading and asynchrony were so difficult, but
> as you point out, you pretty much have to go out of your way to be
> this badly-behaved on Mac OS X.
>
> Let us never speak of it again :-/
>
> Anyone got a good socket framework to recommend? (I realize it's not
> that hard to roll your own with NSStreams, as shown in CocoaSockets,
> but a framework with a few more bells & whistles would be nice.)
>
> —Jens_______________________________________________
>
> Cocoa-dev mailing list (<email_removed>)
>
> Please do not post admin requests or moderator comments to the list.
> Contact the moderators at cocoa-dev-admins(at)lists.apple.com
>
> Help/Unsubscribe/Update your Subscription:
> http://lists.apple.com/mailman/options/cocoa-dev/<email_removed>
>
> This email sent to <email_removed>
| Related mails | Author | Date |
|---|---|---|
| Jens Alfke | May 10, 20:23 | |
| Wade Tregaskis | May 10, 20:59 | |
| Jens Alfke | May 10, 21:11 | |
| Robert Claeson | May 10, 21:18 | |
| Michael Gardner | May 10, 21:35 | |
| Ricky Sharp | May 11, 00:24 |






Cocoa mail archive

