Tried that; no change in behavior. To shed a little light on the actual issue I'm having, consider this scenario:

1. A single threaded/noforking server is running.
2. Two clients are constantly connecting to it, sending TWO lines of text each time, then waits for a response.

What happens is that the first client to connect sends it's two lines, gets it's response, and continues. The second client connects, sends it's two lines, BUT when the server finishes the first client and moves onto the 2nd client, it only sees ONE line of text.

Here's some output that may or may not help:

client 1:
2012-01-06-14.32.08 [Collection..:ConnectToDispatch  184]  Connecting 
+to dispatch at 127.0.0.1 ....
2012-01-06-14.32.08 [                  CS_Server.pl  175]  Consulting 
+Dispatcher
2012-01-06-14.32.08 [Collection..twork::SendMessage  118]  Sending REQ
+UEST_TYPE (10)
2012-01-06-14.32.09 [Collection..ork::SendSocketRow  160]  Sent socket
+ row COLLECTION
2012-01-06-14.32.10 [Collection..RecvAndValidateMsg  130]  Received me
+ssage ACK_REQUEST_TYPE

client 2:
2012-01-06-14.32.13 [Collection..:ConnectToDispatch  184]  Connecting 
+to dispatch at 127.0.0.1 ....
2012-01-06-14.32.13 [                  CS_Server.pl  175]  Consulting 
+Dispatcher
2012-01-06-14.32.13 [Collection..twork::SendMessage  118]  Sending REQ
+UEST_TYPE (10)
2012-01-06-14.32.14 [Collection..ork::SendSocketRow  160]  Sent socket
+ row COLLECTION

server (first client):
2012-01-06-14.32.06 [Collection..CP::AcceptListener   64]  Accepted co
+nnection from 127.0.0.1:1866 (IO::Socket::INET=GLOB(0x1033f3d8))
>>> message is '10
'
2012-01-06-14.32.06 [ Collection::IPC::TCP::Receive  155]  Received '1
+0' from IO::Socket::INET=GLOB(0x1033f3d8)
>>> message is 'COLLECTION
'
2012-01-06-14.32.07 [ Collection::IPC::TCP::Receive  155]  Received 'C
+OLLECTION' from IO::Socket::INET=GLOB(0x1033f3d8)
2012-01-06-14.32.07 [Collection..er::ProcessRequest   90]  Received re
+quest type of 'COLLECTION'
2012-01-06-14.32.07 [    Collection::IPC::TCP::Send  167]  Sending '15
+' to IO::Socket::INET=GLOB(0x1033f3d8)

server (2nd client):
2012-01-06-14.32.11 [Collection..CP::AcceptListener   64]  Accepted co
+nnection from 127.0.0.1:1872 (IO::Socket::INET=GLOB(0x103f1278))
>>> message is '10
'
2012-01-06-14.32.11 [ Collection::IPC::TCP::Receive  155]  Received '1
+0' from IO::Socket::INET=GLOB(0x103f1278)
[download]

No "Received 'COLLECTION'" from that point.

So it appears to me that when a client hasn't been "accept"ed and sends multiple lines of text, only one is being received when it eventually is connected.

That's my issue. I'll continue to go over my code again and see if I'm not doing something stupid, but honestly this is confusing me.

---

---

Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!

Titles consisting of a single word are discouraged, and in most cases are disallowed outright.

Read Where should I post X? if you're not absolutely sure you're posting in the right place.

Please read these before you post! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

Posts may use any of the Perl Monks Approved HTML tags:

a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr

You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)

	For:		Use:
	&		&
	<		&lt;
	>		&gt;
	[		&#91;
	]		&#93;

Link using PerlMonks shortcuts! What shortcuts can I use for linking?

See Writeup Formatting Tips and other pages linked from there for more info.