Thread: Multiple POSIX Timers with handlers: how to?

Oh, yes, I must not implement NAKs in this project, only ACKs. Acknowledgements are cumulative, i.e. if three packets were received, then I'll send ACK for the last (third) packet, which will mean that all tree packets got through. As for congestion: there's a receiver buffer and ACKs have a special field that tell how much more packets the sender can supply to receiver.

Quote: Originally Posted by jpollard Yup - the application specified is using UDP, which doesn't block. That calls for something external to invoke the stall. In this case, I'd suggest a NAK when the count reaches the limit, and drop the data. So much misinformation in such few lines .... /UDP certainly does block, tho' for a smaller set of reasons. This "toy" case is presumable implemented in userspace making...

And none of them implement reliable delivery over UDP without implementing some form of ACK/NAK and sending limits. Reliable delivery of UDP is not a standard... The problem with UDP is that the senders/receivers cannot assume reliable delivery. Reliable delivery can only be supported at the application layer. The original statement was '"pseudo TCP" on top of UDP protocol'. I know TCP works differently. It...

Yes, I could shed some light on the TCP timeout concept but...I am not a guru, so...

I'm not Linus Tornvalds, alias a guru, and so more superficially and with poor knowledge of the subject, I would create a list of objects, with the appropriate functions to manage it (insert, delete, read, write objects, timer, ecc.) and one/more global functions to manage the list. Or if I would have much free time, I would hack some good code written by others.

This is fairly simple to do, but since I'm not a guru then premudriy doesn't want my help.

I'll change the title, as folks seem to be, as you say, overly touchy. Maybe that will help.