On Monday, July 8, 2013 12:59:12 PM UTC-5, Ilia Mirkin wrote:
If this is not an option, you can write a custom decoder that just
skips over fields you don't need to read. This is a little tricky, but
if you're not trying to be too generic it shouldn't be that much code.
Do you have an
On Tue, Jul 9, 2013 at 11:36 AM, phreed phr...@gmail.com wrote:
On Monday, July 8, 2013 12:59:12 PM UTC-5, Ilia Mirkin wrote:
If this is not an option, you can write a custom decoder that just
skips over fields you don't need to read. This is a little tricky, but
if you're not trying to
On Tuesday, July 9, 2013 1:51:51 PM UTC-5, Ilia Mirkin wrote:
On Tue, Jul 9, 2013 at 11:36 AM, phreed phr...@gmail.com javascript:
wrote:
On Monday, July 8, 2013 12:59:12 PM UTC-5, Ilia Mirkin wrote:
If this is not an option, you can write a custom decoder that just
On Tue, Jul 9, 2013 at 4:36 PM, phreed phr...@gmail.com wrote:
On Tuesday, July 9, 2013 1:51:51 PM UTC-5, Ilia Mirkin wrote:
On Tue, Jul 9, 2013 at 11:36 AM, phreed phr...@gmail.com wrote:
My situation is a bit different than the original poster.
I have a set of content sensitive network
This is how I handle the same issue. This would be similar to most
multi-threaded daemons taking client input. The manager reads the message
type and passes the socket/stream to a handling thread.
On Monday, July 8, 2013 10:59:12 AM UTC-7, Ilia Mirkin wrote:
Unfortunately it's not
