> > which may bring us to the point again to re-code fakewap with "real" > WSP and WTP code from the libwap.a libs.
Which means that the "one (or more) threads per stack entity" pattern of doing things in Kannel must go. Writing a client that has to start, manage and terminate dozens of threads is just stupid, when a (not so) simple select loop + state machine would do much better. This is the thrust of my argument that Kannel needs a framework interface for the stack entities that hides the actual implementation of the engine. Regards Joerg
