Michael Clifford a écrit :
Awesome! Thanks! So then is it proper to handle this by using the session as
a key?
ie. Let's say I wanted to save the contents of each input message in a string, one string per session, so that I can then parse the strings using my application's internal protocol.
Why don't you implement the protocol as a filter ? Then your application
will receive a complete valid and decoded message, and no need to do
that matching.
Then I could create a hashmap with the session as the key, and return the
appropriate string from that hashmap to concatenate the appropriate input
string to, and then my internal handlers would do whatever I need to do with
those strings.
if you decide to do that, then store the String in the session, as an
attribute.
