Re: ANN: Etiquette: a protocol construction tool

Luke,

[Insightful comments on lightweight multitasking snipped]

Luke>  The _right_ solution is to have a system that lets you write
Luke>  simple code and have it executed in a select()-loop. Then you
Luke>  get the nice programming interface plus the scalability and
Luke>  robustness. In my opinion implementing such an interface is
Luke>  _the_ most important thing for Etiquette-like frameworks.

OK, the changes you suggest address performance issues and are mostly
orthogonal to the abstractions used in Etiquette, hence such a
threading schema probably can be adopted.

Now, my concern is how much it would limit design space available
to application implementor: networking model is one thing, but I'd
hate to coerce anyone into particular multitasking
implementation. Besides that, doing a framework based on SERVE-EVENT
restricts portability somewhat.

Probably a good idea is to make lightweight threading optional, so
that people could choose the model they prefer. I need to think
seriously about how that could be achieved though.

But in any case, thanks for your comment. Seeing the project from
different angle and understanding people's needs in the problem domain
is extremely helpful.

--
  Eugene