Re: [AOLSERVER] Why limiting the length of cache names to 32 characters

2003-01-08 Thread Scott Goodwin
AOLserver 4.0 hasn't been released -- you can get the code by checking out the "aolserver" module from AOLserver's CVS SourceForge area. /s. On Wednesday, January 8, 2003, at 03:18 PM, Niels Hallenberg wrote: Hi There, On Wed, 8 Jan 2003 14:38:15 EST, Jim Davidson <[EMAIL PROTECTED]> wrote:

Re: [AOLSERVER] Why limiting the length of cache names to 32 characters

2003-01-08 Thread Niels Hallenberg
Hi There, On Wed, 8 Jan 2003 14:38:15 EST, Jim Davidson <[EMAIL PROTECTED]> wrote: >There's no specific reason for the 32byte limit and not checking for overflow >is just a stupid oversight. AOLserver 4.0 has no limit as you suggest - the >cache structure is grown to hold the required number of

Re: [AOLSERVER] Why limiting the length of cache names to 32 characters

2003-01-08 Thread Jim Davidson
In a message dated 1/8/2003 9:27:50 AM Eastern Standard Time, [EMAIL PROTECTED] writes: I'am a co-developer of SMLserver, which is a Standard ML interpreter for AOLserver making it possible to script with Standard ML, see http://www.smlserver.org. Standard ML is a strict typed language, and we tr

Re: [AOLSERVER] Why limiting the length of cache names to 32 characters

2003-01-08 Thread Zoran Vasiljevic
On Wednesday 08 January 2003 16:01, you wrote: > > The reason is that the cache name began to be larger than 32 > characters, and there is no mechanism in the cache API that prevents > this to happen (in particular the call to strcpy in function > CacheCreate line 1197). > > My question is why the

[AOLSERVER] Why limiting the length of cache names to 32 characters

2003-01-08 Thread Niels Hallenberg
Hi There, I'am a co-developer of SMLserver, which is a Standard ML interpreter for AOLserver making it possible to script with Standard ML, see http://www.smlserver.org. Standard ML is a strict typed language, and we try to bring types into most of the interfaces that we build. We are currently w