Author Brian.Cain
Recipients Brian.Cain, Ian.Davis, jnoller, neologix, terry.reedy
Date 2011-04-19.02:54:10
SpamBayes Score 1.72037e-05
Marked as misclassified No
Message-id <BANLkTi=R8RmypH58bVCjaCnGSFskONRkzA@mail.gmail.com>
In-reply-to <1302684710.15.0.312275782078.issue8426@psf.upfronthosting.co.za>
Content
Please don't close the issue.

Joining aside, the basic point ("But when size = 7279, the data submitted
reaches 64k, so the writting thread blocks on the write syscall.") is not
clear from the docs, right?

IMO, it would be nice if I could ask my queue, "Just what is your capacity
(in bytes, not entries) anyways?  I want to know how much I can put in here
without worrying about whether the remote side is dequeueing."  I guess I'd
settle for explicit documentation that the bound exists.  But how should I
expect my code to be portable?  Are there platforms which provide less than
64k?  Less than 1k?  Less than 256 bytes?
Files
File name Uploaded
unnamed Brian.Cain, 2011-04-19.02:54:09
History
Date User Action Args
2011-04-19 02:54:11Brian.Cainsetrecipients: + Brian.Cain, terry.reedy, jnoller, neologix, Ian.Davis
2011-04-19 02:54:10Brian.Cainlinkissue8426 messages
2011-04-19 02:54:10Brian.Caincreate