Greg Stein wrote: [snip] > > And punt that darn state_rec thing. If it is the name, no problem we can discuss that. In various discussions the name suggested was session_rec. This was th original name RyanB and I had. However, some found the name confusing with the sessions as being used in HTTP which are for instance cookies. That was considered a session so we used here state. With respect to eliminating the state_rec as layer, I am wondering how you otherwise will transer data between requests and maintain state. The pool-lifetime is the problem. IMHO, it also maps more cleanly towards the protocols. Harrie
- Apache 2.0 for multi protocol usage Harrie Hazewinkel
- Re: Apache 2.0 for multi protocol usage Bill Stoddard
- Re: Apache 2.0 for multi protocol usage Harrie Hazewinkel
- Re: Apache 2.0 for multi protocol usage Greg Stein
- Re: Apache 2.0 for multi protocol us... rbb
- Re: Apache 2.0 for multi protoc... Greg Stein
- Re: Apache 2.0 for multi pr... Harrie Hazewinkel
- Re: Apache 2.0 for mult... Bill Stoddard
- Re: Apache 2.0 for multi pr... Harrie Hazewinkel
- Re: Apache 2.0 for mult... Greg Stein
- Re: Apache 2.0 for mult... Harrie Hazewinkel
- Re: Apache 2.0 for mult... Greg Stein
- Re: Apache 2.0 for multi pr... rbb
- Re: Apache 2.0 for mult... Greg Stein
- Re: Apache 2.0 for mult... rbb
- Re: Apache 2.0 for mult... William A. Rowe, Jr.
- Re: Apache 2.0 for mult... rbb
- Re: Apache 2.0 for mult... Harrie Hazewinkel
- Re: Apache 2.0 for mult... Marc Slemko
