Ben Gollmer wrote:
> On May 24, 2007, at 8:12 AM, Niklas Therning wrote:
>
>> Ben Gollmer wrote:
>>>
>>> Of course, it probably isn't the best application design to go around
>>> blasting IoSession attributes willy-nilly. However, I know my code,
>>> and nothing else was storing attributes on IoSes
On May 24, 2007, at 8:12 AM, Niklas Therning wrote:
Ben Gollmer wrote:
Of course, it probably isn't the best application design to go around
blasting IoSession attributes willy-nilly. However, I know my code,
and nothing else was storing attributes on IoSessions until I started
working with JM
Ben Gollmer wrote:
> Hi all,
>
> I have an application which reuses IoSessions often. Basically as the
> client sends data, state is built up within the IoSession via a series
> of attributes. When the server recognizes that an event has taken
> place, it processes the session, and clears the attri
Hi all,
I have an application which reuses IoSessions often. Basically as the
client sends data, state is built up within the IoSession via a
series of attributes. When the server recognizes that an event has
taken place, it processes the session, and clears the attributes for
the next ro
