OK, that being the case, I'll recommend that you consider using a database pool and a faux database driver for what you're doing. This will work if you don't require that each visitor have a unique identity to your external system. In this case, AOLserver does a terrific job of managing a pool of external sessions, bringing them up or tearing them down as necessary, based on usage and idle patterns. I've used this method successfully on a few projects.
- Re: [AOLSERVER] GCC compilation of AOLserver 4.x fails du... Scott Goodwin
- [AOLSERVER] How does a module know a GET or POST req... Ramin Naimi
- Re: [AOLSERVER] How does a module know a GET or ... Peter M. Jansson
- Re: [AOLSERVER] How does a module know a GET... Ramin Naimi
- Re: [AOLSERVER] How does a module know a... Peter M. Jansson
- Re: [AOLSERVER] How does a module know a GET... Dossy
- Re: [AOLSERVER] How does a module know a... Peter M. Jansson
- Re: [AOLSERVER] How does a module k... Dossy
- Re: [AOLSERVER] How does a module k... Rusty Brooks
- Re: [AOLSERVER] How does a modu... Peter M. Jansson
- Re: [AOLSERVER] How does a modu... Dossy
- Re: [AOLSERVER] How does a ... Peter M. Jansson
- Re: [AOLSERVER] How does a module know a GET or ... Jim Wilcoxson
- Re: [AOLSERVER] How does a module know a GET... Peter M. Jansson
- Re: [AOLSERVER] How does a module know a... Jim Wilcoxson