Re: [AOLSERVER] Tcl bytecode caching for Tcl pages
Makes sense. So what is cleared up in the interpreter after each request? Looking at the slides, there is a command table and a variable table. Looking at Wojciech's post, it seems any procedures created/packages loaded in the current interpreter stay there, is that correct? And what about variables, are they preserved as well or cleared out? Is there ane special consideration for any namespace variables? (ie: $::foo::bar) Cheers, Bas. Peter M. Jansson said: A new thread gets a new interp, but if you configure the server to start the max number of threads (maxthreads == minthreads), then the server will start all necessary threads at startup. Because of all the copying, thread startup on AOLserver is fairly expensive (close to, if not more expensive than, forking a new process for CGI on a Unix system), so higher-volume sites will start all threads at server start. I. To remove yourself from this list: Send a message to [EMAIL PROTECTED] with the following text in the BODY of your message: signoff aolserver II. For a complete list of listserv options please visit: http://listserv.aol.com/ III. For more AOLserver information please visit: http://www.aolserver.com/
Re: [AOLSERVER] Tcl bytecode caching for Tcl pages
Bas Scheffers wrote:
Makes sense. So what is cleared up in the interpreter after each request?
Looking at the slides, there is a command table and a variable table.
Looking at Wojciech's post, it seems any procedures created/packages
loaded in the current interpreter stay there, is that correct?
From what I noticed, procs stay, variables not, however nothing outside
global namespace is cleaned up. This is imho good, since packages can
store data in namespaced variables.
I think it would be reasonable to develop some package loading/saving
feature. I could code one (better one than I have now) in C (speed
issues), but never had the time. My current ns_pkg is at
www.nsstuff.zoro.tcl.pl, if anyone's interested.
And what about variables, are they preserved as well or cleared out?
Is there ane special consideration for any namespace variables?
(ie: $::foo::bar)
This one showed that no namespaced variables are cleaned up by AOLserver
% namespace eval z {} %
::a %=[info exists ::a]%BR
::z::a %=[info exists ::z::a]%BR
% set ::a b %
% set ::z::a b %
After about 100 requests the results were:
::a 0
::z::a 1
(at the beginning it was 0 0)
--
WK
(written at Stardate 57153.5)
Data typing is an illusion. Everything is a sequence of bytes.
-Todd Coram
I. To remove yourself from this list:
Send a message to [EMAIL PROTECTED] with the following text in
the BODY of your message:
signoff aolserver
II. For a complete list of listserv options please visit:
http://listserv.aol.com/
III. For more AOLserver information please visit:
http://www.aolserver.com/
Re: [AOLSERVER] Tcl bytecode caching for Tcl pages
Wojciech Kocjan said: From what I noticed, procs stay, variables not, however nothing outside global namespace is cleaned up. This is imho good, since packages can store data in namespaced variables. Cool, so seems it's just a cleanup of everything in [info globals]. That's good to know! Bas. I. To remove yourself from this list: Send a message to [EMAIL PROTECTED] with the following text in the BODY of your message: signoff aolserver II. For a complete list of listserv options please visit: http://listserv.aol.com/ III. For more AOLserver information please visit: http://www.aolserver.com/
Re: [AOLSERVER] Tcl bytecode caching for Tcl pages
On Tuesday 25 February 2003 12:52, you wrote: I think it would be reasonable to develop some package loading/saving feature. I could code one (better one than I have now) in C (speed issues), but never had the time. My current ns_pkg is at www.nsstuff.zoro.tcl.pl, if anyone's interested. The 4.0 series does much better job in interp initialization. This is now more/less entirely under Tcl control so you can adjust it to suit your own needs. Speed is IMHO, dependent on the size of interp state which needs to be re-created. With some C-level code you won't be able to speed-up things that much that it would justify the effort needed. I'd say, people should start looking at 4.0 and see how we can improve what's there, if it ain't sufficient and/or not fast enough. I've heard from Jeff, that ActiveState is working (or has already) an Tcl_CloneInterp() (or similar) function coded in C. This might be something to consider as well. Cheers Zoran I. To remove yourself from this list: Send a message to [EMAIL PROTECTED] with the following text in the BODY of your message: signoff aolserver II. For a complete list of listserv options please visit: http://listserv.aol.com/ III. For more AOLserver information please visit: http://www.aolserver.com/
Re: [AOLSERVER] nsjava calling tcl functions
On Mon, 24 Feb 2003 18:41:04 +0100, Branimir Dolicki [EMAIL PROTECTED] wrote: Just curious: why are you asking? Are there any problems with servlets? No problems other than lack of support for anything newer than Tomcat 3 (with older nstomcat module). I am working on nsjk2 module which is compatible with Tomcat 4 and respective Java Servlet and JSP spec. Alex I. To remove yourself from this list: Send a message to [EMAIL PROTECTED] with the following text in the BODY of your message: signoff aolserver II. For a complete list of listserv options please visit: http://listserv.aol.com/ III. For more AOLserver information please visit: http://www.aolserver.com/
[AOLSERVER] Root-server switches from BIND to NSD.
http://slashdot.org/comments.pl?sid=55040threshold=-1commentsort=3tid=185mode=threadpid=5379648 Well this isn't really as true or good as I wish it was. The nsd in this case is not the naviserver daemon we all enjoy but a nameserver daemon written at NLnet Labs in cooperation with RIPE. http://www.nlnetlabs.nl/nsd/index.html They say, NSD is an authoratative only, high performance, simple and open source name server. And they're not using tinydns either, although if you look at the first few slides in their presentation, the slides look as though they may have come directly from tiny documentation! http://www.ripe.net/ripe/meetings/archive/ripe-42/presentations/ripe42-dns-aons/ Hmmmph! Jerry I. To remove yourself from this list: Send a message to [EMAIL PROTECTED] with the following text in the BODY of your message: signoff aolserver II. For a complete list of listserv options please visit: http://listserv.aol.com/ III. For more AOLserver information please visit: http://www.aolserver.com/
Re: [AOLSERVER] Root-server switches from BIND to NSD.
On 2003.02.25, Jerry Asher [EMAIL PROTECTED] wrote: The nsd in this case is not the naviserver daemon we all enjoy but a nameserver daemon written at NLnet Labs in cooperation with RIPE. Should we add to the confusion and start coding up an nsdns module so one could use AOLserver to serve DNS? :-) If there was an nsudp socket, we could implement a DNS server that runs out of AOLserver that could use any nsdb to store zone data in a DBMS ... that might be mildly interesting. -- Dossy -- Dossy Shiobara mail: [EMAIL PROTECTED] Panoptic Computer Network web: http://www.panoptic.com/ He realized the fastest way to change is to laugh at your own folly -- then you can let go and quickly move on. (p. 70) I. To remove yourself from this list: Send a message to [EMAIL PROTECTED] with the following text in the BODY of your message: signoff aolserver II. For a complete list of listserv options please visit: http://listserv.aol.com/ III. For more AOLserver information please visit: http://www.aolserver.com/
Re: [AOLSERVER] Root-server switches from BIND to NSD.
Dossy wrote: On 2003.02.25, Jerry Asher wrote: The nsd in this case is not the naviserver daemon we all enjoy but a nameserver daemon written at NLnet Labs in cooperation with RIPE. Should we add to the confusion and start coding up an nsdns module so one could use AOLserver to serve DNS? :-) Imagine the additional confusion and flames regarding security when we announce our new version is based on nsd 8. Jerry I. To remove yourself from this list: Send a message to [EMAIL PROTECTED] with the following text in the BODY of your message: signoff aolserver II. For a complete list of listserv options please visit: http://listserv.aol.com/ III. For more AOLserver information please visit: http://www.aolserver.com/
[AOLSERVER] namespace?
I'm still trying to understand exactly what good namespace really is. What are the advantages? Any examples of what it can be used for? Are there any performance considerations? I. To remove yourself from this list: Send a message to "[EMAIL PROTECTED]" with the following text in the BODY of your message: signoff aolserver II. For a complete list of listserv options please visit: http://listserv.aol.com/ III. For more AOLserver information please visit: http://www.aolserver.com/
[AOLSERVER] Will pay for Informix driver update
I'm looking for someone to update the Informix driver for AOLserver. I have up to $3000 for the job. I would like ACS/OpenACS style bind variable interface if possible. I haven't checked to see if Informix has something similar to Oracle's bind variables. I also want blob support and the ability to use stored procedures. The code would stay open source and hopefully be hosted on sourceforge. I am in the process of setting up a Sun Solaris 9 box with Informix 9.3 server and documentation which will be available for development/testing. The developer will need to sign a consulting agreement before I can turn them loose on our server. I realize this may be more than a $3000 job. But hey, it will more than pay for the Coke you drink while you do the job. I wouldn't mind if someone could do it for less either. If you would like to take a look at the existing driver code let me know and I'll get you a copy. I tried this once before but the money didn't materialize. Now I finally have the funding in place. I hope someone with AOLserver db driver experience can find the time. Keith Paskett [EMAIL PROTECTED] I. To remove yourself from this list: Send a message to [EMAIL PROTECTED] with the following text in the BODY of your message: signoff aolserver II. For a complete list of listserv options please visit: http://listserv.aol.com/ III. For more AOLserver information please visit: http://www.aolserver.com/
Re: [AOLSERVER] Root-server switches from BIND to NSD.
Dossy [EMAIL PROTECTED] writes: If there was an nsudp socket, we could implement a DNS server that runs out of AOLserver that could use any nsdb to store zone data in a DBMS ... that might be mildly interesting. Really cool, in fact! If it were efficient enough, it would save the trouble of generating BIND zone files from an RDBMS; you would access the database from within AOLserver, and cache zones in nsdns according to their TTLs -- but using the NOTIFY mechanism of the RDBMS to make sure updates were made available immediately anyway. I like it! It can't be too hard to do, can it? -tih -- Tom Ivar Helbekkmo, Senior System Administrator, EUnet Norway www.eunet.no T: +47-22092958 M: +47-93013940 F: +47-22092901 I. To remove yourself from this list: Send a message to [EMAIL PROTECTED] with the following text in the BODY of your message: signoff aolserver II. For a complete list of listserv options please visit: http://listserv.aol.com/ III. For more AOLserver information please visit: http://www.aolserver.com/
Re: [AOLSERVER] Root-server switches from BIND to NSD.
On Tuesday, February 25, 2003, at 03:05 PM, Rob Mayoff wrote: +-- On Feb 25, Dossy said: Added bonus would be a web interface for viewing zones and editing them, which would persist changes back down to the DBMS. Note that a web interface to your DNS data doesn't require that AOLserver respond to DNS requests. Among others, there's a SourceForge project called BIND-DLZ in which BIND serves records directly from a database, without needing zone files, and without having to declare all your zones in a config file prior to startup, so you can add zones just by updating the database. This would probably be easier to use in concert with an AOLserver front end than trying to get AOLserver to speak DNS correctly. (DNS is not a trivial protocol.) Now, better resolver support in AOLserver, allowing for concurrent resolution requests -- that's worth doing! I. To remove yourself from this list: Send a message to [EMAIL PROTECTED] with the following text in the BODY of your message: signoff aolserver II. For a complete list of listserv options please visit: http://listserv.aol.com/ III. For more AOLserver information please visit: http://www.aolserver.com/
Re: [AOLSERVER] Root-server switches from BIND to NSD.
- Original Message - From: Rob Mayoff [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Tuesday, February 25, 2003 1:07 PM Subject: Re: [AOLSERVER] Root-server switches from BIND to NSD. +-- On Feb 25, Patrick Spence said: I'd certainly be willing to use it here :) it would be a lot easier to administer than bind is for me.. There are alternatives to BIND that many consider easier to administer. I am using a gui interface (webmin) to bind already, but I am also using Daniel Stasinski's NS/Admin module for administering postgresql, and its easy for me to use and familiar to me, so if I can consolidate what I am doing into a single common interface it makes it easier.. I. To remove yourself from this list: Send a message to [EMAIL PROTECTED] with the following text in the BODY of your message: signoff aolserver II. For a complete list of listserv options please visit: http://listserv.aol.com/ III. For more AOLserver information please visit: http://www.aolserver.com/
Re: [AOLSERVER] namespace?
I'm still trying to understand exactly what good namespace really is. What are the advantages? Any examples of what it can be used for? It is just useful for code encapsulation, so you can create procs without the worry of having other code with similar proc names stomp on it. Are there any performance considerations? Very minor, way too insignificat to worry about. Jeff I. To remove yourself from this list: Send a message to [EMAIL PROTECTED] with the following text in the BODY of your message: signoff aolserver II. For a complete list of listserv options please visit: http://listserv.aol.com/ III. For more AOLserver information please visit: http://www.aolserver.com/
