what server are you talking to? I was just trying to undesrtand that example I'm learning POE it's pretty rare to use something that low level I might have to though just like you don't put your car together from steel and rubber in your garage. :) why might? I'm making an MMO engine, with client/server you're using something besides the 50 protocols already supported? client will be done in C and opengl by someone else I believe that is correct (the $_[SENDER] session within poco-server-tcp's ClientConnected client session is the parent poco-server-tcp session). What would you sugggest? I'd sugest using Jabber or HTTP beteween your engines or even KIC IKC IKC rocks oh ok I never considered that you can use plugin protocols on client and server * amnesiac has quit ("Leaving") * amnesiac (n=amnesiac@p3m/member/Amnesiac) has joined #perl I imageine the person doing the C client wont have trouble finding libs for a common protocol either it's actually quite tricky to designing a protocol * adrakoa has quit (Success) yeah we were planning it out like have a byte saying how the long the data field will be yeah, if you have random guys connecting, I'd really strongly suggest http or jabber error code byte etc http? thats interesting heh - the 80's called... they want your designs back HTTP is a nice protocol * chovy_ has quit ("leaving") clear metadata multiple binary payloads and can be routed through proxies and over SSL easily you dont think it would add to much overhead