Re: Mysterious socket error

I believe I've solved (or at least papered over) the problems I was seeing
by doing my own rigorous locking before I even start looking at a frame in
pfa().  Now only one thread can get anywhere useful in pfa() on a given
message at one time, and I am not misplacing messages, nor am I getting
dropped sessions, at least not in moderate testing.

Although it would seem this sort of per-message locking should not even be
needed, since I've worked around it, the main problem I have to complain
about now is the still unexplained frame fragmentation that beepcore-c is
doing to even small (<2K) messages.  I expect it hurts performance and
should be something I can avoid.  I may have time to pursue it myself in a
few months, but in the mean time everyone should be aware that it is
lurking.  For those people doing message-oriented stuff rather than
frame-oriented, I'd guess it is afflicting you as well, but it is
low-level enough you don't notice.

-------------------------------------------------------
-- David C. Niemi           Adeptech Systems, Inc.   --
-- Reston, Virginia, USA    http://www.adeptech.com/ --
-------------------------------------------------------



-------------------------------------------------------
This SF.net email is sponsored by: Perforce Software.
Perforce is the Fast Software Configuration Management System offering
advanced branching capabilities and atomic changes on 50+ platforms.
Free Eval! http://www.perforce.com/perforce/loadprog.html