> > > > 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. > > yep... sounds like you're volonteering for contributing patches/code?? > ;)
Maybe. I have something on my disk, but it's not yet ready for prime time. Regards Joerg
