Re: [AOLSERVER] Fun, free applications for building personal sites.

2008-05-06 Thread Brett Schwarz
I don't think TclSOAP uses tdom, does it? That might explain any speed problems.

In addition there is Web Services for Tcl: 
http://members.cox.net/~gerald.lester/WebServicesForTcl.html

I have not used it at all, so I can't offer any opinion...however it does look 
like it uses tdom.

- Original Message 
From: Rusty Brooks [EMAIL PROTECTED]
To: AOLSERVER@LISTSERV.AOL.COM
Sent: Monday, May 5, 2008 8:04:10 PM
Subject: Re: [AOLSERVER] Fun, free applications for building personal sites.

I've used TclSoap.  I wasn't like, impressed with it's speed but it seems OK.  
It seems quite behind the 
times, though, I did extensive modifications trying to get it to work with 
various WSDL files and in general 
it does not do a complete job, which is kind of frustrating, especially when 
integrating with web services 
that have TONS of data types and commands.  It kind of looked like that WSDL 
implementation just didn't 
progress past a certain point.  I might screw with it some time but at the 
moment I've got the manual soap 
definitions done for the apps I need to support, so, it's not that pressing.

Bas Scheffers wrote:
 On 06/05/2008, at 11:44 AM, Tom Jackson wrote:
 The main thing you need with a mashup is data. Without that, there is 
 nothing
 to mash.
 And much of that data is in XML and tdom runs rings around any Java XML 
 implementation, though not sure about the ones in PHP, Perl, etc which 
 are also likely to be C based. (I am currently profiling and optimizing 
 a car rentals aggregator site, which does tons of XML parsing and 
 creating. Its all in Java and its not pretty; sooo slow and with 
 enormous RAM requirements)
 
 Has anyone used TclSOAP? And compared it in performance to Java SOAP 
 clients?
 
 Bas.
 
 
 -- 
 AOLserver - http://www.aolserver.com/
 
 To Remove yourself from this list, simply send an email to 
 [EMAIL PROTECTED] with the
 body of SIGNOFF AOLSERVER in the email message. You can leave the 
 Subject: field of your email blank.


--
AOLserver - http://www.aolserver.com/

To Remove yourself from this list, simply send an email to [EMAIL PROTECTED] 
with the
body of SIGNOFF AOLSERVER in the email message. You can leave the Subject: 
field of your email blank.



  

Be a better friend, newshound, and 
know-it-all with Yahoo! Mobile.  Try it now.  
http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ


--
AOLserver - http://www.aolserver.com/

To Remove yourself from this list, simply send an email to [EMAIL PROTECTED] 
with the
body of SIGNOFF AOLSERVER in the email message. You can leave the Subject: 
field of your email blank.


Re: [AOLSERVER] Fun, free applications for building personal sites.

2008-05-06 Thread Tom Jackson
On Monday 05 May 2008 22:58, Brett Schwarz wrote:
 I don't think TclSOAP uses tdom, does it? That might explain any speed
 problems.

 In addition there is Web Services for Tcl:
 http://members.cox.net/~gerald.lester/WebServicesForTcl.html

 I have not used it at all, so I can't offer any opinion...however it does
 look like it uses tdom.

Right Web Services for Tcl requires Tcl 8.5 and tclhttpd, it doesn't work with 
AOLserver.

tom jackson


--
AOLserver - http://www.aolserver.com/

To Remove yourself from this list, simply send an email to [EMAIL PROTECTED] 
with the
body of SIGNOFF AOLSERVER in the email message. You can leave the Subject: 
field of your email blank.


Re: [AOLSERVER] Fix for ns_tmpnam under Windows

2008-05-06 Thread Gustaf Neumann

fixed.
-gustaf neumann

Titi Alailima schrieb:

There is a missing variable declaration in this patch for i, the for-loop 
index.  Anyone want to make this fix and commit it?
  



--
AOLserver - http://www.aolserver.com/

To Remove yourself from this list, simply send an email to [EMAIL PROTECTED] 
with the
body of SIGNOFF AOLSERVER in the email message. You can leave the Subject: 
field of your email blank.


Re: [AOLSERVER] Fun, free applications for building personal sites.

2008-05-06 Thread Stefan Sobernig

Bas,


In addition there is Web Services for Tcl:
http://members.cox.net/~gerald.lester/WebServicesForTcl.html

I have not used it at all, so I can't offer any opinion...however it does
look like it uses tdom.


Right Web Services for Tcl requires Tcl 8.5 and tclhttpd, it doesn't work with 
AOLserver.




Besides, Web Services for Tcl is based upon the TclOO package by Donal 
K. Fellows which is not (besides other issues) multi-threading/ 
AOLServer compatible (no serializer etc.)


You might want to check out xotcl-soap (xosoap) as well which comes as 
OpenACS package: see http://alice.wu-wien.ac.at:8000/xorb-doc/




I don't think TclSOAP uses tdom, does it? That might explain any speed problems.


Indeed, TclSOAP is built around TclDOM/TclXML and suggests one of the 
two C-based DOM backends: http://wiki.tcl.tk/9098



Has anyone used TclSOAP? And compared it in performance to Java SOAP clients?


I do not have a direct comparison, but probably some rough benchmark:
http://www.extreme.indiana.edu/xgws/soap_bench/linux_loopback/index.html
(the accompanying paper is also a good introductory read)

Generally speaking, and according to the benchmark above, Java-based 
environments (Axis 1.2 at that time) are (across all benchmark types) 
less performant than c/c++ based ones (gSOAP), by factors of ~7 
(latency) and 10-15+ (end-to-end roundtrip, i.e. including 
de/marshalling, arrays of ints + strings). The picture certainly changed 
since 2004 because  parsing (streaming parsers) and optimisation 
techniques (differential marshaling) gained momentum in Java-based 
toolkits, but it shows a tendency. Besides, memory footprint is not 
considered in the above benchmark which might be even more important 
than processing time depending on your requirements.


We are currently working on a performance evaluation of xotcl-soap. 
First, tentative results show that xotcl-soap settles in the inbetween 
the two benchmark ends above, in the lower third of this range. But, 
again, the test setting is not directly comparable. I will report back 
if there is interest. Moreover, we work on optimisations (differential 
marshaling using adp templating, for instance) that might promise 
speed-ups by a factor of 10 in certain settings.


//stefan
--
Stefan Sobernig
Institute for Information Systems and New Media
Vienna University of Economics  
Augasse 2-6
A - 1090 Vienna

`- +43 - 1 - 31336 - 4878 [phone]
`- +43 - 1 - 31336 - 746 [fax]
`- [EMAIL PROTECTED] mailto:[EMAIL PROTECTED]
`- [EMAIL PROTECTED] mailto:[EMAIL PROTECTED]


--
AOLserver - http://www.aolserver.com/

To Remove yourself from this list, simply send an email to [EMAIL PROTECTED] 
with the
body of SIGNOFF AOLSERVER in the email message. You can leave the Subject: 
field of your email blank.


Re: [AOLSERVER] Fun, free applications for building personal sites.

2008-05-06 Thread Brett Schwarz


 - Original Message 
 From: Tom Jackson [EMAIL PROTECTED]
 To: AOLSERVER@LISTSERV.AOL.COM
 Sent: Monday, May 5, 2008 11:46:47 PM
 Subject: Re: [AOLSERVER] Fun, free applications for building personal sites.

 On Monday 05 May 2008 22:58, Brett Schwarz wrote:
  I don't think TclSOAP uses tdom, does it? That might explain any speed
  problems.
 
  In addition there is Web Services for Tcl:
  http://members.cox.net/~gerald.lester/WebServicesForTcl.html
 
  I have not used it at all, so I can't offer any opinion...however it does
  look like it uses tdom.

 Right Web Services for Tcl requires Tcl 8.5 and tclhttpd, it doesn't work with
 AOLserver.

Tcl 8.5 *or* the _dict (source, windows binary) extension for Tcl 8.4_

I can't imagine that it would take too much to make it work with aolserver...in 
fact I believe
the main author of that package is using aolserver now, but I'm not sure if he 
has ported this over to aolserver.


  

Be a better friend, newshound, and 
know-it-all with Yahoo! Mobile.  Try it now.  
http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ


--
AOLserver - http://www.aolserver.com/

To Remove yourself from this list, simply send an email to [EMAIL PROTECTED] 
with the
body of SIGNOFF AOLSERVER in the email message. You can leave the Subject: 
field of your email blank.


Re: [AOLSERVER] Fun, free applications for building personal sites.

2008-05-06 Thread Brett Schwarz
  In addition there is Web Services for Tcl:
  http://members.cox.net/~gerald.lester/WebServicesForTcl.html
 
  I have not used it at all, so I can't offer any opinion...however it does
  look like it uses tdom.
 
  Right Web Services for Tcl requires Tcl 8.5 and tclhttpd, it doesn't work 
  with
  AOLserver.
 

 Besides, Web Services for Tcl is based upon the TclOO package by Donal
 K. Fellows which is not (besides other issues) multi-threading/
 AOLServer compatible (no serializer etc.)


huh? Where did you get that it is based on TclOO? TclOO isn't even out yet. And 
where did
you get that TclOO is not compatible with aolserver...just curious (I haven't 
tried it myself within aolserver). It should be thread safe, as far as I'm 
aware (although I don't believe it is fully implemented yet, so you never know).



  

Be a better friend, newshound, and 
know-it-all with Yahoo! Mobile.  Try it now.  
http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ


--
AOLserver - http://www.aolserver.com/

To Remove yourself from this list, simply send an email to [EMAIL PROTECTED] 
with the
body of SIGNOFF AOLSERVER in the email message. You can leave the Subject: 
field of your email blank.


Re: [AOLSERVER] Fun, free applications for building personal sites.

2008-05-06 Thread Tom Jackson
On Tuesday 06 May 2008 02:18, Stefan Sobernig wrote:
 Besides, Web Services for Tcl is based upon the TclOO package by Donal
 K. Fellows which is not (besides other issues) multi-threading/
 AOLServer compatible (no serializer etc.)

Web Services for Tcl isn't based on TclOO and it doesn't have any issues with 
multi-threading. The client works great. I have used it to test all of my 
WSDL example services. 

Here is an example of how to use it:

http://junom.com/document/windows/TWiST/WS::Client.TXT

I think I just used the ActiveTcl version of Tcl8.5. 

I'm not sure what it means to not have a serializer. Once WS::Client gets the 
WSDL file, you can create 'stubs' for each operation. Then you just feed it a 
list (without the element names, just data). A 'dictionary' is returned, 
which includes the element names (usually this could be fed directly to 
[array create] for simple structures). 

The problem with the WS::Server running with AOLserver is that it uses the 
tclhttpd API for I/O (biggest problem), but also uses many tclhttpd'isms to 
create web pages for documentation, etc. 

tWSDL with the TWiST API has a very thin connection to AOLserver. The same 
services, with the same TWiST configuration file can run under nstclsh, 
tclsh, tcpserver or even using a shell pipeline. The tclsh version can run 
using Tcl socket, or using Tcl Threads (recommended).

The tcpserver version is great during application development because 
everything is sourced up from scratch for each request. 

As a WSDL server, the best feature of tWSDL is that you can define and derive 
types based upon the XML-Schema definitions, and you can validate documents 
against the type. Once defined, types are easy to create  by feeding the 
type's 'new' API with a Tcl list (with no element info, just data).

I haven't found any other WSDL toolkit which can derive simple types from 
XML-Schema types or easily create complexTypes where minOccurs  1. With 
tWSDL a single TWiST 'configuration' file completely defines the web service 
interface, there is no hand writing WSDL files or hand coding type 
validation, and your internal API remain independent of the external 
operation interface. 

tom jackson


--
AOLserver - http://www.aolserver.com/

To Remove yourself from this list, simply send an email to [EMAIL PROTECTED] 
with the
body of SIGNOFF AOLSERVER in the email message. You can leave the Subject: 
field of your email blank.


Re: [AOLSERVER] Fun, free applications for building personal sites.

2008-05-06 Thread Tom Jackson
On Tuesday 06 May 2008 07:17, Tom Jackson wrote:
 I haven't found any other WSDL toolkit which can derive simple types from
 XML-Schema types or easily create complexTypes where minOccurs  1.

Oops, I meant to say maxOccurs  1. XML-Schema structural type serialization 
is complicated. To do it correctly you have to know minOccurs, maxOccurs, if 
the element is nillable, the default value (for tcl, if the default is the 
empty string), and of course the data being serialized. 

tom jackson


--
AOLserver - http://www.aolserver.com/

To Remove yourself from this list, simply send an email to [EMAIL PROTECTED] 
with the
body of SIGNOFF AOLSERVER in the email message. You can leave the Subject: 
field of your email blank.


Re: [AOLSERVER] Fun, free applications for building personal sites.

2008-05-06 Thread Rusty Brooks
I don't need it as a server, I need it as a client.  You mentioned something a bout being able to use the API 
to make a client?


Rusty

Tom Jackson wrote:

Following up on my previous post about tWSDL...

If you guys are actually using WSDL, please look at tWSDL. It functions very 
well as a server. But internally you can define/derive types as described in 
the XML-Schema types/structures standards. Once defined, you can create and 
validate types (including correct handling of min/maxOccurs, isnull, etc.)


tom jackson 



On Monday 05 May 2008 20:04, Rusty Brooks wrote:

I've used TclSoap.  I wasn't like, impressed with it's speed but it seems
OK.  It seems quite behind the times, though, I did extensive modifications
trying to get it to work with various WSDL files and in general it does not
do a complete job, which is kind of frustrating, especially when
integrating with web services that have TONS of data types and commands. 
It kind of looked like that WSDL implementation just didn't progress past a

certain point.  I might screw with it some time but at the moment I've got
the manual soap definitions done for the apps I need to support, so, it's
not that pressing.

Bas Scheffers wrote:

On 06/05/2008, at 11:44 AM, Tom Jackson wrote:

The main thing you need with a mashup is data. Without that, there is
nothing
to mash.

And much of that data is in XML and tdom runs rings around any Java XML
implementation, though not sure about the ones in PHP, Perl, etc which
are also likely to be C based. (I am currently profiling and optimizing
a car rentals aggregator site, which does tons of XML parsing and
creating. Its all in Java and its not pretty; sooo slow and with
enormous RAM requirements)

Has anyone used TclSOAP? And compared it in performance to Java SOAP
clients?

Bas.


--
AOLserver - http://www.aolserver.com/

To Remove yourself from this list, simply send an email to
[EMAIL PROTECTED] with the
body of SIGNOFF AOLSERVER in the email message. You can leave the
Subject: field of your email blank.

--
AOLserver - http://www.aolserver.com/

To Remove yourself from this list, simply send an email to
[EMAIL PROTECTED] with the body of SIGNOFF AOLSERVER in the
email message. You can leave the Subject: field of your email blank.



--
AOLserver - http://www.aolserver.com/

To Remove yourself from this list, simply send an email to [EMAIL PROTECTED] 
with the
body of SIGNOFF AOLSERVER in the email message. You can leave the Subject: 
field of your email blank.



--
AOLserver - http://www.aolserver.com/

To Remove yourself from this list, simply send an email to [EMAIL PROTECTED] 
with the
body of SIGNOFF AOLSERVER in the email message. You can leave the Subject: 
field of your email blank.


Re: [AOLSERVER] Fun, free applications for building personal sites.

2008-05-06 Thread Stefan Sobernig

Besides, Web Services for Tcl is based upon the TclOO package by Donal
K. Fellows which is not (besides other issues) multi-threading/
AOLServer compatible (no serializer etc.)



huh? Where did you get that it is based on TclOO? TclOO isn't even out yet. 


My fault. The only and first time I stumbled over Gerald's Web Services 
for Tcl was in Donal's tcl2007 presentation on TclOO*. Therefore, my 
misunderstanding ...



And where did

you get that TclOO is not compatible with aolserver...just curious (I haven't 
tried it myself within aolserver). It should be thread safe, as far as I'm 
aware (although I don't believe it is fully implemented yet, so you never know).


I'm not sure what it means to not have a serializer. 


Let me rephrase, it is not said that it is not compatible (nothing to do 
with thread safety or anything in that direction), I am just saying that 
it might need some integration work. By serialiser, I am referring to
the needed generation of the ns_ictl script in the aolserver driver 
thread. But, it goes without saying, this is just one option ...


* 
http://www.tcl.tk/community/tcl2007/proceedings/programmingtechniques/OOforTclFellows.pdf

--
Stefan Sobernig
Institute for Information Systems and New Media
Vienna University of Economics  
Augasse 2-6
A - 1090 Vienna

`- +43 - 1 - 31336 - 4878 [phone]
`- +43 - 1 - 31336 - 746 [fax]
`- [EMAIL PROTECTED] mailto:[EMAIL PROTECTED]
`- [EMAIL PROTECTED] mailto:[EMAIL PROTECTED]


--
AOLserver - http://www.aolserver.com/

To Remove yourself from this list, simply send an email to [EMAIL PROTECTED] 
with the
body of SIGNOFF AOLSERVER in the email message. You can leave the Subject: 
field of your email blank.


Re: [AOLSERVER] Fun, free applications for building personal sites.

2008-05-06 Thread Tom Jackson
Rusty,

Yes, there is a start of a client, which downloads, and parses a WSDL file. 

But there are so many poorly defined services, and so many options which you 
could use in a web service, that it hasn't been a priority to create a 
generic client.

Instead I'm leaning toward redefining an external service using the TWiST API, 
and with tiny changes (like the URL of the original service), use a TWiST 
server as a proxy for the external service. 

In fact, this type of client already exists in TWiST which allows for testing 
the service via a web interface. 

( See the example operations at http://junom.com/ws/mywebservice/ )

The testing interface is just a web page with a simple form. When the form is 
submitted, the values are translated into a client request, which is POSTed 
back to the same server (a seperate request). The only change needed for a 
proxy would be the external URL used for POSTing the request. Slowly this is 
coming together in the wsclient API (which will be similar to wsreturn ).

tom jackson

On Tuesday 06 May 2008 07:50, Rusty Brooks wrote:
 I don't need it as a server, I need it as a client.  You mentioned
 something a bout being able to use the API to make a client?


--
AOLserver - http://www.aolserver.com/

To Remove yourself from this list, simply send an email to [EMAIL PROTECTED] 
with the
body of SIGNOFF AOLSERVER in the email message. You can leave the Subject: 
field of your email blank.


Re: [AOLSERVER] Fun, free applications for building personal sites.

2008-05-06 Thread Tom Jackson
On Tuesday 06 May 2008 08:22, Stefan Sobernig wrote:
 Let me rephrase, it is not said that it is not compatible (nothing to do
 with thread safety or anything in that direction), I am just saying that
 it might need some integration work. By serialiser, I am referring to
 the needed generation of the ns_ictl script in the aolserver driver
 thread. But, it goes without saying, this is just one option ...

Well, it would require something more like a major rewrite. It was written for 
tclhttpd and the tclhttpd API are used for I/O. The service configuration 
files are written for tclhttpd as well, so those would have to be modified. 

But, it is a simple piece of software, only a few pages, just very brittle to 
external details. 

The client works great! I would recommend it as a first thing to try before 
investigating anything else. 

tom jackson


--
AOLserver - http://www.aolserver.com/

To Remove yourself from this list, simply send an email to [EMAIL PROTECTED] 
with the
body of SIGNOFF AOLSERVER in the email message. You can leave the Subject: 
field of your email blank.


Re: [AOLSERVER] Fun, free applications for building personal sites.

2008-05-06 Thread Stefan Sobernig

Tom,


Let me rephrase, it is not said that it is not compatible (nothing to do
with thread safety or anything in that direction), I am just saying that
it might need some integration work. By serialiser, I am referring to
the needed generation of the ns_ictl script in the aolserver driver
thread. But, it goes without saying, this is just one option ...


Well, it would require something more like a major rewrite. 


MY rephrasing on integration relates to TclOO and Brett's:


And where did
you get that TclOO is not compatible with aolserver...just curious (I haven't 
tried it myself within aolserver).


... NOT Web Services for Tcl ... just to avoid misunderstandings ...

//stefan

--
Stefan Sobernig
Institute for Information Systems and New Media
Vienna University of Economics  
Augasse 2-6
A - 1090 Vienna

`- +43 - 1 - 31336 - 4878 [phone]
`- +43 - 1 - 31336 - 746 [fax]
`- [EMAIL PROTECTED] mailto:[EMAIL PROTECTED]
`- [EMAIL PROTECTED] mailto:[EMAIL PROTECTED]


--
AOLserver - http://www.aolserver.com/

To Remove yourself from this list, simply send an email to [EMAIL PROTECTED] 
with the
body of SIGNOFF AOLSERVER in the email message. You can leave the Subject: 
field of your email blank.


Re: [AOLSERVER] Fun, free applications for building personal sites.

2008-05-06 Thread Tom Jackson
On Tuesday 06 May 2008 09:57, Stefan Sobernig wrote:
 Tom,

  Let me rephrase, it is not said that it is not compatible (nothing to do
  with thread safety or anything in that direction), I am just saying that
  it might need some integration work. By serialiser, I am referring to
  the needed generation of the ns_ictl script in the aolserver driver
  thread. But, it goes without saying, this is just one option ...
 
  Well, it would require something more like a major rewrite.

 MY rephrasing on integration relates to TclOO and Brett's:
  And where did
  you get that TclOO is not compatible with aolserver...just curious (I
  haven't tried it myself within aolserver).

 ... NOT Web Services for Tcl ... just to avoid misunderstandings ...

Hmmm, why would using TclOO or any other Tcl code require doing anything with 
the driver thread, or require using ns_ictl? I still don't get what a 
serializer is. 

Is this one of those object system 'isms?

tom jackson


--
AOLserver - http://www.aolserver.com/

To Remove yourself from this list, simply send an email to [EMAIL PROTECTED] 
with the
body of SIGNOFF AOLSERVER in the email message. You can leave the Subject: 
field of your email blank.


[AOLSERVER] Rolling logs in Windows

2008-05-06 Thread Titi Alailima
Anyone know how to signal nsd in Windows to roll the logs?  Any equivalent of 
kill -HUP?

Titi Ala'ilima
Lead Architect
MedTouch LLC
1100 Massachusetts Avenue
Cambridge, MA 02138
617.621.8670 x309



--
AOLserver - http://www.aolserver.com/

To Remove yourself from this list, simply send an email to [EMAIL PROTECTED] 
with the
body of SIGNOFF AOLSERVER in the email message. You can leave the Subject: 
field of your email blank.


Re: [AOLSERVER] Rolling logs in Windows

2008-05-06 Thread Titi Alailima
Not quite.   I get a permission error renaming the old file.  I'm running as a 
service from the local System account.  Any ideas why it can't rename the 
file even though it can create, remove and write to files?

Regardless, I was wondering if there was a way from the OS to send the 
NS_SIGHUP signal.  Doesn't look like it if I read the source correctly.

Titi Ala'ilima
Lead Architect
MedTouch LLC
1100 Massachusetts Avenue
Cambridge, MA 02138
617.621.8670 x309

 -Original Message-
 From: AOLserver Discussion [mailto:[EMAIL PROTECTED] On
 Behalf Of Tom Jackson
 Sent: Tuesday, May 06, 2008 3:50 PM
 To: AOLSERVER@LISTSERV.AOL.COM
 Subject: Re: [AOLSERVER] Rolling logs in Windows

 Does ns_logroll work?

 http://rmadilo.com/files/nsapi/ns_logroll.html

 tom jackson

 On Tuesday 06 May 2008 12:12, Titi Alailima wrote:
  Anyone know how to signal nsd in Windows to roll the logs?  Any
 equivalent
  of kill -HUP?
 
  Titi Ala'ilima
  Lead Architect
  MedTouch LLC
  1100 Massachusetts Avenue
  Cambridge, MA 02138
  617.621.8670 x309
 
 
 
  --
  AOLserver - http://www.aolserver.com/
 
  To Remove yourself from this list, simply send an email to
  [EMAIL PROTECTED] with the body of SIGNOFF AOLSERVER in
 the
  email message. You can leave the Subject: field of your email blank.


 --
 AOLserver - http://www.aolserver.com/

 To Remove yourself from this list, simply send an email to
 [EMAIL PROTECTED] with the
 body of SIGNOFF AOLSERVER in the email message. You can leave the
 Subject: field of your email blank.


--
AOLserver - http://www.aolserver.com/

To Remove yourself from this list, simply send an email to [EMAIL PROTECTED] 
with the
body of SIGNOFF AOLSERVER in the email message. You can leave the Subject: 
field of your email blank.


Re: [AOLSERVER] Fun, free applications for building personal sites.

2008-05-06 Thread Stefan Sobernig

Tom,

I still don't get what a 
serializer is. 

Is this one of those object system 'isms?


Well, no ... it is not an *ism in the sense of peculiar feature of an 
object-based/oriented system. Streaming an in-memory state into a set of 
characters based on run-time introspection is not a trait of OO. But for 
OO, take a look at:


http://www.riehle.org/computer-science/research/1996/plop-1996-serializer.html

Hmmm, why would using TclOO or any other Tcl code require doing anything with 
the driver thread, or require using ns_ictl? 


I assume that you are familiar AOLServer blueprinting mechanism? Tcl 
introspection (info) is used to stream the state of the interpreter in 
the driver/main thread of AOLServer to the connection/scheduler/... 
threads (and beyond, if you take Zoran's tclthread extension into 
account) early in their life-cycle. This happens in 
init.tcl-_ns_savenamespaces and helpers. So, in AOLServer Tcl's info + 
_ns_* family of procs + Tcl's eval represent a procedural serializer. 
But, as Tcl's info cannot introspect on the XOTcl/TclOO object system, 
these object systems need to provide their own facility to re-create the 
object graph (objects + relations) in terms of a script. Take a look at 
generic/aol-xotcl.tcl in the XOTcl source distribution, it amends 
standard _ns_savenamespace by a call to the xotcl Serializer object.


So, unless you don't want to call package req on XOTcl/TclOO in each 
connection thread interpreter and want your AOLserver OO-Tcl Module 
available in AOLServer workers, you need to provide a serialiser. Or, 
you have the nifty feature of ttrace that comes with Naviserver. Either 
way is a design problem of its own and non-trivial (especially in the OO 
case). See the enlightening discussing over at naviserver-devel:


http://www.mail-archive.com/[EMAIL PROTECTED]/msg00136.html


--
AOLserver - http://www.aolserver.com/

To Remove yourself from this list, simply send an email to [EMAIL PROTECTED] 
with the
body of SIGNOFF AOLSERVER in the email message. You can leave the Subject: 
field of your email blank.


Re: [AOLSERVER] Rolling logs in Windows

2008-05-06 Thread Titi Alailima
I think the renaming fails because Windows is picky about not messing with 
files that are open.  Can we close the log file before rolling?  Seems like 
nslog does this for the access log.  Just needs to be done similarly in 
nsd/log.c.  That might require copying a bunch of stuff over from nslog.c or 
putting the common code somewhere else.  There's certainly seems to be a lot of 
redundancy between the two sets of code, a great candidate for streamlining.

Titi Ala'ilima
Lead Architect
MedTouch LLC
1100 Massachusetts Avenue
Cambridge, MA 02138
617.621.8670 x309


 -Original Message-
 From: AOLserver Discussion [mailto:[EMAIL PROTECTED] On
 Behalf Of Titi Alailima
 Sent: Tuesday, May 06, 2008 5:18 PM
 To: AOLSERVER@LISTSERV.AOL.COM
 Subject: Re: [AOLSERVER] Rolling logs in Windows

 Not quite.   I get a permission error renaming the old file.  I'm
 running as a service from the local System account.  Any ideas why it
 can't rename the file even though it can create, remove and write to
 files?

 Regardless, I was wondering if there was a way from the OS to send the
 NS_SIGHUP signal.  Doesn't look like it if I read the source correctly.

 Titi Ala'ilima
 Lead Architect
 MedTouch LLC
 1100 Massachusetts Avenue
 Cambridge, MA 02138
 617.621.8670 x309

  -Original Message-
  From: AOLserver Discussion [mailto:[EMAIL PROTECTED] On
  Behalf Of Tom Jackson
  Sent: Tuesday, May 06, 2008 3:50 PM
  To: AOLSERVER@LISTSERV.AOL.COM
  Subject: Re: [AOLSERVER] Rolling logs in Windows
 
  Does ns_logroll work?
 
  http://rmadilo.com/files/nsapi/ns_logroll.html
 
  tom jackson
 
  On Tuesday 06 May 2008 12:12, Titi Alailima wrote:
   Anyone know how to signal nsd in Windows to roll the logs?  Any
  equivalent
   of kill -HUP?
  
   Titi Ala'ilima
   Lead Architect
   MedTouch LLC
   1100 Massachusetts Avenue
   Cambridge, MA 02138
   617.621.8670 x309
  
  
  
   --
   AOLserver - http://www.aolserver.com/
  
   To Remove yourself from this list, simply send an email to
   [EMAIL PROTECTED] with the body of SIGNOFF AOLSERVER in
  the
   email message. You can leave the Subject: field of your email
 blank.
 
 
  --
  AOLserver - http://www.aolserver.com/
 
  To Remove yourself from this list, simply send an email to
  [EMAIL PROTECTED] with the
  body of SIGNOFF AOLSERVER in the email message. You can leave the
  Subject: field of your email blank.


 --
 AOLserver - http://www.aolserver.com/

 To Remove yourself from this list, simply send an email to
 [EMAIL PROTECTED] with the
 body of SIGNOFF AOLSERVER in the email message. You can leave the
 Subject: field of your email blank.


--
AOLserver - http://www.aolserver.com/

To Remove yourself from this list, simply send an email to [EMAIL PROTECTED] 
with the
body of SIGNOFF AOLSERVER in the email message. You can leave the Subject: 
field of your email blank.


Re: [AOLSERVER] Rolling logs in Windows

2008-05-06 Thread Tom Jackson
On Tuesday 06 May 2008 19:23, Titi Alailima wrote:
 I think the renaming fails because Windows is picky about not messing with
 files that are open.  Can we close the log file before rolling?  Seems like
 nslog does this for the access log.  Just needs to be done similarly in
 nsd/log.c.  That might require copying a bunch of stuff over from nslog.c
 or putting the common code somewhere else.  There's certainly seems to be a
 lot of redundancy between the two sets of code, a great candidate for
 streamlining.

My guess is that it would be better to keep the two chunks of code distinct. I 
seem to remember that they are not that similar anyway. (For one, a single 
nsd can have multiple access.log files, but only one server.log file.)

tom jackson


--
AOLserver - http://www.aolserver.com/

To Remove yourself from this list, simply send an email to [EMAIL PROTECTED] 
with the
body of SIGNOFF AOLSERVER in the email message. You can leave the Subject: 
field of your email blank.