Re: cfsocket / upd monitoring
Re: cfsocket / upd monitoring
- Subject: Re: cfsocket / upd monitoring
- From: Stephane Huaulme <email@hidden>
- Date: Tue, 24 Jun 2003 11:41:58 -0500
Yes, I meant UDP. I understand that it is not reliable, but I was not
expecting to loose data in very low traffic / low cpu activity cases.
The broadcast is between the broadcasting device and the computer,
there is nothing else on that network so there is no possibility for a
collision.
is there any way to garanty that the runloop is given the appropriate
time to handle CFSocket? does anyone knows how deep the buffers on the
ethernet hardware receiver are?
In the case of TCP traffic, if I'm waiting for a packet, what is the
best way to give the runloop time to monitor the CFSocket (I'm using
runUntilDate, but I was wondering if there was a better way)?
On Tuesday, June 24, 2003, at 10:28 AM, Kaelin Colclasure wrote:
On Monday, June 23, 2003, at 02:51 PM, Stephane Huaulme wrote:
I'm using cfsocket to monitor a upd based broadcast and at times, I
miss small sparse packets (50 bytes per second type activity). the
cpu is not very busy (25% average) at the time. I suspect that the
problem may be due to some conflicting higher priority task that
prevents the runloop of my app to pick up the small upd packets in
time. Does anyone have any suggestions how to solve this one?
I am guessing you mean 'UDP' not 'UPD'... :-) Keep in mind, that 'U'
stands for Unreliable. Most likely what you are seeing is packets lost
due to collisions, busy routers, etc.
-- Kaelin
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.