>> Well, choosing a suitable Data Structure to support all this will >> again be interesting. Current implementation uses something similar to >> LinkedHashtable. Have to see if something simpler can be implemented >> or out of the box API :-) > > > It's my opinion that new filters get created to simulate state machine > changes and any other use is an ad hoc mechanism that can be more cleanly > refactored into a state machine mechanism. With that said aa session w/ N > fixed chains where each chain represents a state would fit the bill. The > number of states is fixed. The composition of the state machine can be > changed until the acceptor/connector have established the connection. > > Acceptor -> ChainMachine -> IoHandler > > inside the chain machine: > > S1: IOF1 -> IOF2 -> IOF3 -> IOF5 -> IOF4 > S2: IOF1 -> IOF3 -> IOF5 -> IOF4 > S3: IOF1 -> IOF2 -> IOF3 -> IOF4 > > From a user's perspective things are quite easy to grok and most cases the > chain machine degenerates into a single state chain.
Agree on point that we have to keep additional noise away :-) So what's the best way proceed forward, now that we had a quite a good discussion :-) -- thanks ashish
