Re: [AOLSERVER] ns_cond, threads and file descriptors.

2001-04-19 Thread Jim Davidson
In a message dated 4/19/2001 12:03:25 AM Eastern Daylight Time, [EMAIL PROTECTED] writes: > From:Peter Harper <[EMAIL PROTECTED]> > Subject: ns_cond, threads and file descriptors. > > I've been trying to find a solution to the following problem... > > I have two message queues in shared memo

Re: [AOLSERVER] TCL namespaces/packages in AOLserver

2001-04-19 Thread Daniƫl Mantione
On Thu, 19 Apr 2001, Michael A. Cleverly wrote: > Some are undoubtedly left over from the AOLserver 2.x days when Tcl 7.4 > did not have many functions that have since been added (in 7.6 & 8.x). > There is no real reason for [ns_time] over [clock seconds], but the former > persists for compatabil

Re: [AOLSERVER] TCL namespaces/packages in AOLserver

2001-04-19 Thread Michael A. Cleverly
On Thu, 19 Apr 2001, Tomasz Kosiak wrote: > I also wonder why there are ns_* commands that accomplish the same > that standard TCL commands (ex. [ns_unlink] and [file > delete]. Browsing AOLserver sources revealed that some TCL procs are > not thread-safe. Isn't better to make them thread-safe so

[AOLSERVER] TCL namespaces/packages in AOLserver

2001-04-19 Thread Tomasz Kosiak
I refer in this post to AOLserver branch nsd_v3_r3_p0 at SourceForge which has some bugfixes to TCL namespace mechanism (when compared to AOLserver 3.2). For details see: http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/aolserver/aolserver/tcl/Attic/namespace.tcl?only_with_tag=nsd_v3_r3_p0&hideatti

Re: [AOLSERVER] ADP new line..

2001-04-19 Thread Rob Mayoff
> ooppsss .XML-RPC parser So what? You can put HTML inside a tag or a tag in XML-RPC. If it's a tag, put the HTML in a CDATA section. If it's a tag, then encode it using ns_uuencode (which actually does base-64 encoding). > > > ill be passing that string to an XML parser i may en

Re: [AOLSERVER] Help on Oracle8 driver for WinNT needed

2001-04-19 Thread Rob Mayoff
> Can you guess what has gone wrong? Don't make us guess. Delete your server log, try starting the server again, put the ENTIRE new server log on the web somewhere, and post the URL.