https://panoptic.com/mediawiki/aolserver/api.php?action=feedcontributions&feedformat=atom&user=CavemanAOLserver Wiki - User contributions [en]2026-06-09T05:45:45ZUser contributionsMediaWiki 1.34.2https://panoptic.com/mediawiki/aolserver/index.php?title=User_talk:Akhassin&diff=5461User talk:Akhassin2009-10-13T16:01:47Z<p>Caveman: </p>
<hr />
<div>Thanks for the recent updates! --[[User:Caveman|Caveman]] 12:01, 13 October 2009 (EDT)</div>Cavemanhttps://panoptic.com/mediawiki/aolserver/index.php?title=Writing_your_first_C_module&diff=5413Writing your first C module2009-10-08T20:00:37Z<p>Caveman: </p>
<hr />
<div>The AOLServer C API is very easy to develop towards. This short tutorial takes you through construction of an "nshello" module that provides a "ns_hello" function.<br />
<br />
NOTE: This has been updated for aolserver4.5 (ns.mak) --[[User:Caveman|Caveman]] 15:49, 8 October 2009 (EDT)<br />
<br />
Step 0: Requirements<br />
<br />
You need (at least) ns.h and ns.mak.<br />
<br />
On Debian, simply:<br />
<br />
<pre>apt-get install aolserver4-dev</pre><br />
<br />
Step 1: Write your module code, "nshello.c" (this can be any name you like):<br />
<br />
<pre><br />
<br />
/*<br />
* Get the data types and constants you will need later on,<br />
* such as Tcl_Interp and NS_OK.<br />
*/<br />
#include "ns.h"<br />
<br />
#include <string.h><br />
#include <sys/types.h><br />
<br />
/*<br />
* Each module asserts its version via the required Ns_ModuleVersion variable<br />
*/<br />
int Ns_ModuleVersion = 1;<br />
<br />
/*<br />
* Declare that this module will implement this initialization method.<br />
*/<br />
int Ns_ModuleInit(char *hServer, char *hModule);<br />
<br />
/*<br />
* This can be named whatever you like, it is used during module initialisation<br />
* to contain specific initialisation steps for the Tcl interpreter itself,<br />
* such as registering commands like "ns_hello".<br />
*/<br />
static int HelloInterpInit(Tcl_Interp *interp, void *context);<br />
<br />
/*<br />
* Declare a C function that will be bound to the "ns_hello" Tcl command. It can be<br />
* named whatever you like as well.<br />
*/<br />
static int HelloCmd(ClientData context, Tcl_Interp *interp, int argc, char **argv);<br />
<br />
/*<br />
* Implement the Ns_ModuleInit function we declared we would implement earlier.<br />
* This is called by the server right after the module is loaded. Here, you<br />
* can read configuration data, initialise internal data, and of course<br />
* register any Tcl commands.<br />
*/<br />
int Ns_ModuleInit(char *hServer, char *hModule)<br />
{<br />
<br />
/*<br />
* Invoke the server's Tcl interpreter initialisation and pass<br />
* it the callback we defined to our own interpreter initialisation.<br />
*/<br />
return (Ns_TclInitInterps(hServer, HelloInterpInit, NULL));<br />
<br />
}<br />
<br />
/*<br />
* Implement the interpreter initialisation we declared and passed<br />
* during module init. Use Tcl_CreateCommand to register<br />
* the command "ns_hello", passing a callback to "HelloCmd" which<br />
* we declared earlier.<br />
*/<br />
static int HelloInterpInit(Tcl_Interp *interp, void *context)<br />
{<br />
Tcl_CreateCommand(interp, "ns_hello", HelloCmd, NULL, NULL);<br />
<br />
return NS_OK;<br />
}<br />
<br />
<br />
/*<br />
* Append "hello" and then all arguments to the result.<br />
*/<br />
static int HelloCmd(ClientData context, Tcl_Interp *interp, int argc, char **argv)<br />
{<br />
int i;<br />
<br />
Tcl_AppendResult(interp, "hello", NULL);<br />
<br />
for (i = 0; i < argc; i++)<br />
{<br />
Tcl_AppendResult(interp, " ", NULL);<br />
Tcl_AppendResult(interp, argv[i], NULL);<br />
}<br />
<br />
return NS_OK;<br />
}<br />
</pre><br />
<br />
That's it. That's an entire module.<br />
<br />
Step 2: Build your module.<br />
<br />
AOLServer includes a meta-Makefile '''Makefile.module''' that simplifies the construction of module makefiles. Simply define a few values in your owm Makefile, then include this meta-Makefile.<br />
<br />
<pre><br />
<br />
#<br />
# Module name<br />
#<br />
MOD = nshello<br />
<br />
#<br />
# Objects to build<br />
# .o will be matched to .c files<br />
#<br />
OBJS = nshello.o<br />
<br />
#<br />
# Header files in THIS directory<br />
#<br />
HDRS =<br />
<br />
#<br />
# Extra libraries<br />
#<br />
MODLIBS =<br />
<br />
<br />
#<br />
# Compiler flags<br />
#<br />
CFLAGS =<br />
<br />
include /usr/share/aolserver4/ns.mk<br />
</pre><br />
<br />
Done. Now you can build your module with 'make'.<br />
<br />
You should now have a nifty "nshello.so" shared object library sitting around. Copy "nshello.so" to /usr/lib/aolserver4/bin (or where you keep your server modules).<br />
<br />
Step 3: Tell aolserver to load the module (/etc/aolserver4/aolserver4.tcl):<br />
<br />
<pre><br />
ns_section "ns/server/${servername}/modules"<br />
ns_param nshello nshello.so<br />
</pre><br />
<br />
Done. Restart aolserver and check the log file for errors.<br />
<br />
Step 4: Use the function "ns_hello" in an ADP script:<br />
<br />
<pre><br />
<%<br />
ns_adp_puts [ns_hello "AOLServer module" "world!"]<br />
%><br />
</pre><br />
<br />
Whoa! You get a strange result: hello ns_hello AOLServer module world!<br />
<br />
Notice that "ns_hello" in there? That's because argv[0] is actually the name of the function used to call your interpreter! So, keep that in mind and happy AOLServer module hacking!<br />
<br />
'''Continued Topics'''<br />
<br />
Calling Tcl from within your module (i.e. call ns_rand from your module).<br />
<br />
Reading configuration sections during initialisation.<br />
<br />
Linking to other C libraries in the build process (e.g. linking with libpng).<br />
<br />
[[Embedding a new programming language as a module]].</div>Cavemanhttps://panoptic.com/mediawiki/aolserver/index.php?title=Talk:Module_inclusion&diff=5412Talk:Module inclusion2009-10-08T19:53:24Z<p>Caveman: added log snippet which adds no real information</p>
<hr />
<div>I'm having trouble using something which worked in aolserver4 with aolserver4.5 -- for example my 'writing your first C module' article:<br />
<br />
http://panoptic.com/wiki/aolserver/Writing_your_first_C_module<br />
<br />
<pre><br />
[08/Oct/2009:19:46:30][26013.18446744072300399344][-main-] Notice: modload: loading '/usr/lib/aolserver4/bin/nsperm.so'<br />
[08/Oct/2009:19:46:30][26013.18446744072300399344][-main-] Notice: modload: loading '/usr/lib/aolserver4/bin/nstokyo.so'<br />
[08/Oct/2009:19:46:30][26013.18446744072300399344][-main-] Warning: modload: could not load /usr/lib/aolserver4/bin/nstokyo.so: libnstokyo.so: cannot open shared object file: No such file or directory<br />
[08/Oct/2009:19:46:30][26013.18446744072300399344][-main-] Fatal: modload: failed to load module 'nstokyo.so'<br />
</pre><br />
<br />
Ends up with the nshello.so module being attempted loaded but searching for libnshello.so as well, which fails -- has the C module build and deployment changed? --[[User:Caveman|Caveman]] 15:41, 8 October 2009 (EDT)</div>Cavemanhttps://panoptic.com/mediawiki/aolserver/index.php?title=Writing_your_first_C_module&diff=5411Writing your first C module2009-10-08T19:49:42Z<p>Caveman: corrected to use aolserver4.5 ns.mk</p>
<hr />
<div>The AOLServer C API is very easy to develop towards. This short tutorial takes you through construction of an "nshello" module that provides a "ns_hello" function.<br />
<br />
NOTE: This has been updated for aolserver4.5 (ns.mk) --[[User:Caveman|Caveman]] 15:49, 8 October 2009 (EDT)<br />
<br />
Step 0: Requirements<br />
<br />
You need (at least) ns.h and Makefile.module.<br />
<br />
On Debian, simply:<br />
<br />
<pre>apt-get install aolserver4-dev</pre><br />
<br />
Step 1: Write your module code, "nshello.c" (this can be any name you like):<br />
<br />
<pre><br />
<br />
/*<br />
* Get the data types and constants you will need later on,<br />
* such as Tcl_Interp and NS_OK.<br />
*/<br />
#include "ns.h"<br />
<br />
#include <string.h><br />
#include <sys/types.h><br />
<br />
/*<br />
* Each module asserts its version via the required Ns_ModuleVersion variable<br />
*/<br />
int Ns_ModuleVersion = 1;<br />
<br />
/*<br />
* Declare that this module will implement this initialization method.<br />
*/<br />
int Ns_ModuleInit(char *hServer, char *hModule);<br />
<br />
/*<br />
* This can be named whatever you like, it is used during module initialisation<br />
* to contain specific initialisation steps for the Tcl interpreter itself,<br />
* such as registering commands like "ns_hello".<br />
*/<br />
static int HelloInterpInit(Tcl_Interp *interp, void *context);<br />
<br />
/*<br />
* Declare a C function that will be bound to the "ns_hello" Tcl command. It can be<br />
* named whatever you like as well.<br />
*/<br />
static int HelloCmd(ClientData context, Tcl_Interp *interp, int argc, char **argv);<br />
<br />
/*<br />
* Implement the Ns_ModuleInit function we declared we would implement earlier.<br />
* This is called by the server right after the module is loaded. Here, you<br />
* can read configuration data, initialise internal data, and of course<br />
* register any Tcl commands.<br />
*/<br />
int Ns_ModuleInit(char *hServer, char *hModule)<br />
{<br />
<br />
/*<br />
* Invoke the server's Tcl interpreter initialisation and pass<br />
* it the callback we defined to our own interpreter initialisation.<br />
*/<br />
return (Ns_TclInitInterps(hServer, HelloInterpInit, NULL));<br />
<br />
}<br />
<br />
/*<br />
* Implement the interpreter initialisation we declared and passed<br />
* during module init. Use Tcl_CreateCommand to register<br />
* the command "ns_hello", passing a callback to "HelloCmd" which<br />
* we declared earlier.<br />
*/<br />
static int HelloInterpInit(Tcl_Interp *interp, void *context)<br />
{<br />
Tcl_CreateCommand(interp, "ns_hello", HelloCmd, NULL, NULL);<br />
<br />
return NS_OK;<br />
}<br />
<br />
<br />
/*<br />
* Append "hello" and then all arguments to the result.<br />
*/<br />
static int HelloCmd(ClientData context, Tcl_Interp *interp, int argc, char **argv)<br />
{<br />
int i;<br />
<br />
Tcl_AppendResult(interp, "hello", NULL);<br />
<br />
for (i = 0; i < argc; i++)<br />
{<br />
Tcl_AppendResult(interp, " ", NULL);<br />
Tcl_AppendResult(interp, argv[i], NULL);<br />
}<br />
<br />
return NS_OK;<br />
}<br />
</pre><br />
<br />
That's it. That's an entire module.<br />
<br />
Step 2: Build your module.<br />
<br />
AOLServer includes a meta-Makefile '''Makefile.module''' that simplifies the construction of module makefiles. Simply define a few values in your owm Makefile, then include this meta-Makefile.<br />
<br />
<pre><br />
<br />
#<br />
# Module name<br />
#<br />
MOD = nshello<br />
<br />
#<br />
# Objects to build<br />
# .o will be matched to .c files<br />
#<br />
OBJS = nshello.o<br />
<br />
#<br />
# Header files in THIS directory<br />
#<br />
HDRS =<br />
<br />
#<br />
# Extra libraries<br />
#<br />
MODLIBS =<br />
<br />
<br />
#<br />
# Compiler flags<br />
#<br />
CFLAGS =<br />
<br />
include /usr/share/aolserver4/ns.mk<br />
</pre><br />
<br />
Done. Now you can build your module with 'make'.<br />
<br />
You should now have a nifty "nshello.so" shared object library sitting around. Copy "nshello.so" to /usr/lib/aolserver4/bin (or where you keep your server modules).<br />
<br />
Step 3: Tell aolserver to load the module (/etc/aolserver4/aolserver4.tcl):<br />
<br />
<pre><br />
ns_section "ns/server/${servername}/modules"<br />
ns_param nshello nshello.so<br />
</pre><br />
<br />
Done. Restart aolserver and check the log file for errors.<br />
<br />
Step 4: Use the function "ns_hello" in an ADP script:<br />
<br />
<pre><br />
<%<br />
ns_adp_puts [ns_hello "AOLServer module" "world!"]<br />
%><br />
</pre><br />
<br />
Whoa! You get a strange result: hello ns_hello AOLServer module world!<br />
<br />
Notice that "ns_hello" in there? That's because argv[0] is actually the name of the function used to call your interpreter! So, keep that in mind and happy AOLServer module hacking!<br />
<br />
'''Continued Topics'''<br />
<br />
Calling Tcl from within your module (i.e. call ns_rand from your module).<br />
<br />
Reading configuration sections during initialisation.<br />
<br />
Linking to other C libraries in the build process (e.g. linking with libpng).<br />
<br />
[[Embedding a new programming language as a module]].</div>Cavemanhttps://panoptic.com/mediawiki/aolserver/index.php?title=Talk:Module_inclusion&diff=5410Talk:Module inclusion2009-10-08T19:41:13Z<p>Caveman: added query about 4.0 to 4.5 changes in C modules</p>
<hr />
<div>I'm having trouble using something which worked in aolserver4 with aolserver4.5 -- for example my 'writing your first C module' article:<br />
<br />
http://panoptic.com/wiki/aolserver/Writing_your_first_C_module<br />
<br />
Ends up with the nshello.so module being attempted loaded but searching for libnshello.so as well, which fails -- has the C module build and deployment changed? --[[User:Caveman|Caveman]] 15:41, 8 October 2009 (EDT)</div>Cavemanhttps://panoptic.com/mediawiki/aolserver/index.php?title=User_talk:Akhassin&diff=5409User talk:Akhassin2009-10-08T18:56:38Z<p>Caveman: simple 'thanks' for recent updates</p>
<hr />
<div>Thanks for the recent updates!</div>Cavemanhttps://panoptic.com/mediawiki/aolserver/index.php?title=Ns_schedule_daily&diff=5408Ns schedule daily2009-10-08T18:55:04Z<p>Caveman: removed SPAM link to research papers site</p>
<hr />
<div>Man page: http://aolserver.com/docs/tcl/ns_schedule_daily.html<br />
<br />
----<br />
<br />
'''NAME'''<br />
<br />
: ns_schedule_daily - Schedule a script to run daily at a certain time<br />
<br />
'''SYNOPSIS'''<br />
<br />
: '''ns_schedule_daily''' ''?-once? ?-thread? hour minute script''<br />
<br />
'''DESCRIPTION'''<br />
<br />
: This command schedules a ''script'' to be run at a certain ''hour'' and ''minute'' of the day. Returns the ID of the newly scheduled script. If ''-once'' is specified, then the script is run once and then unscheduled, otherwise it will continue to run every day at that time. If ''-thread'' is specified, then the script will be run in its own thread, otherwise it will run in the scheduler's thread. If the script is long-running, this may interfere with the running of other scheduled scripts, so long-running scripts should be run in their own threads.<br />
<br />
: '''NOTE:''' ''hour'' and ''minute'' are specified in local time. Beware of Daylight Savings Time shifts affecting the time of day when the script will execute.<br />
<br />
'''EXAMPLES'''<br />
<br />
% set id [[ns_schedule_daily -once 5 35 { ns_log notice "It is now 5:35 AM." }]]<br />
123<br />
<br />
% ns_unschedule_proc $id<br />
<br />
'''SEE ALSO'''<br />
<br />
: [[ns_after]], [[ns_info]] scheduled, [[ns_pause]], [[ns_resume]], [[ns_schedule_proc]], [[ns_schedule_weekly]], [[ns_unschedule_proc]]<br />
<br />
----<br />
<br />
[[Category:Documentation]] - [[Category:Core Tcl API]]</div>Cavemanhttps://panoptic.com/mediawiki/aolserver/index.php?title=AOLserver_Wiki&diff=5407AOLserver Wiki2009-10-08T18:53:46Z<p>Caveman: /* AOLserver Resources: */ removed 'sample essays' SPAM link</p>
<hr />
<div>'''[http://www.aolserver.com AOLserver] is a high performance web server with a powerful customization API. The AOLserver Wiki is a comprehensive resource for all things AOLserver.'''<br />
<br />
If you're new to [[wiki]]'s, then [[Welcome, New Visitors]]! Before you start editing, you may want to read over the [[Formatting Rules]]. To find pages grouped by category, [[Special:Categories|start here]].<br />
<br />
== Topics of Conversation ==<br />
<br />
* [[What is AOLserver]]?<br />
* What [[Web Applications for AOLserver]] would you like to see? <br />
* What [[AOLserver Bugs and Problems]] are you experiencing? <br />
* What features does AOLserver need? Add them to the [[AOLserver Wishlist]]. <br />
<br />
* [[What's new in 4.5]] -- New features in version 4.5 of AOLserver. This is the current major release of AOLserver.<br />
<br />
== AOLserver Resources: ==<br />
<br />
* [[Downloads]] -- Access to various AOLserver files and resources.<br />
* [[Modules]] -- Complete list of '''over 70''' AOLserver extension modules and other [[AOLserver Contributed Software]].<br />
* [[Toolkits]] -- Everything you need to build a complete website, fast.<br />
* [[Languages]] -- Build websites in a varierty of different programming languages.<br />
* [[Documentation]] -- Tcl and C API references, tutorials and guides.<br />
* [[FAQ]] -- Frequently Asked Questions about AOLserver.<br />
* [[AOLserver Improvement Proposals]]<br />
* The [[AOLserver Cookbook]] -- A collection of questions, and code examples to answer them.<br />
* [[AOLserver Packages]] -- Binary distributions of AOLserver in popular package management formats.<br />
* [[Useful Links]]<br />
* [http://panoptic.com/wiki/aolserver/Special:Recentchanges?feed=rss RSS 2.0 syndication] of this wiki's recent changes.<br />
<br />
== Developers' Guide (A Work In Progress) ==<br />
<br />
* [[AOLserver Developer's Guide]] -- A growing, community generated guide on how to develop, deploy and maintain applications using AOLserver including discussions of internals, troubleshooting, debugging, testing and tuning.<br />
<br />
== AOLserver Community ==<br />
<br />
* The AOLserver project [[Roadmap]], as well as the planned [[Features]] and changes.<br />
* The [[People]] who work on and contribute to AOLserver, organized into [[Project Teams]].<br />
* Come join us in our [http://www.aolserver.com/chat/ online chat], or just read the [http://panoptic.com/aolserver/chat/ chat logs]. You can participate on the chat either via IRC (irc.freenode.net:6667 #aolserver) or via AIM.<br />
* There's also an [http://www.livejournal.com/community/aolserver/ AOLserver LiveJournal community].<br />
* [[Sites That Run On AOLserver]]<br />
* The [[OpenACS]] Project.<br />
* The [[ProjectOpen]] Project (project management based on [[OpenACS]])<br />
* [[AOLserver User Groups]]<br />
* [[AOLserver Jobs]]<br />
<br />
== AOLserver Core Developers ==<br />
<br />
* [[Vision Statement]]<br />
* [[CVS Commit Guidelines]]<br />
* [http://www.aolserver.com/docs/devel/tech/standards.html AOLserver Engineering Standards Manual]<br />
<br />
__NOTOC__</div>Cavemanhttps://panoptic.com/mediawiki/aolserver/index.php?title=AOLserver_Wiki&diff=5406AOLserver Wiki2009-10-08T18:51:36Z<p>Caveman: /* AOLserver Resources: */ removed 'research papers' SPAM link from Al</p>
<hr />
<div>'''[http://www.aolserver.com AOLserver] is a high performance web server with a powerful customization API. The AOLserver Wiki is a comprehensive resource for all things AOLserver.'''<br />
<br />
If you're new to [[wiki]]'s, then [[Welcome, New Visitors]]! Before you start editing, you may want to read over the [[Formatting Rules]]. To find pages grouped by category, [[Special:Categories|start here]].<br />
<br />
== Topics of Conversation ==<br />
<br />
* [[What is AOLserver]]?<br />
* What [[Web Applications for AOLserver]] would you like to see? <br />
* What [[AOLserver Bugs and Problems]] are you experiencing? <br />
* What features does AOLserver need? Add them to the [[AOLserver Wishlist]]. <br />
<br />
* [[What's new in 4.5]] -- New features in version 4.5 of AOLserver. This is the current major release of AOLserver.<br />
<br />
== AOLserver Resources: ==<br />
<br />
* [[Downloads]] -- Access to various AOLserver files and resources.<br />
* [[Modules]] -- Complete list of '''over 70''' AOLserver extension modules and other [[AOLserver Contributed Software]].<br />
* [[Toolkits]] -- Everything you need to build a complete website, fast.<br />
* [[Languages]] -- Build websites in a varierty of different programming languages.<br />
* [[Documentation]] -- Tcl and C API references, tutorials and guides.<br />
* [[FAQ]] -- Frequently Asked Questions about AOLserver.<br />
* [[AOLserver Improvement Proposals]]<br />
* The [[AOLserver Cookbook]] -- A collection of questions, and code examples to answer them.<br />
* [[AOLserver Packages]] -- Binary distributions of AOLserver in popular package management formats.<br />
* [[Useful Links]]-sample [http://www.bestessays.co.uk Essays]<br />
* [http://panoptic.com/wiki/aolserver/Special:Recentchanges?feed=rss RSS 2.0 syndication] of this wiki's recent changes.<br />
<br />
== Developers' Guide (A Work In Progress) ==<br />
<br />
* [[AOLserver Developer's Guide]] -- A growing, community generated guide on how to develop, deploy and maintain applications using AOLserver including discussions of internals, troubleshooting, debugging, testing and tuning.<br />
<br />
== AOLserver Community ==<br />
<br />
* The AOLserver project [[Roadmap]], as well as the planned [[Features]] and changes.<br />
* The [[People]] who work on and contribute to AOLserver, organized into [[Project Teams]].<br />
* Come join us in our [http://www.aolserver.com/chat/ online chat], or just read the [http://panoptic.com/aolserver/chat/ chat logs]. You can participate on the chat either via IRC (irc.freenode.net:6667 #aolserver) or via AIM.<br />
* There's also an [http://www.livejournal.com/community/aolserver/ AOLserver LiveJournal community].<br />
* [[Sites That Run On AOLserver]]<br />
* The [[OpenACS]] Project.<br />
* The [[ProjectOpen]] Project (project management based on [[OpenACS]])<br />
* [[AOLserver User Groups]]<br />
* [[AOLserver Jobs]]<br />
<br />
== AOLserver Core Developers ==<br />
<br />
* [[Vision Statement]]<br />
* [[CVS Commit Guidelines]]<br />
* [http://www.aolserver.com/docs/devel/tech/standards.html AOLserver Engineering Standards Manual]<br />
<br />
__NOTOC__</div>Cavemanhttps://panoptic.com/mediawiki/aolserver/index.php?title=User_talk:Caveman&diff=5405User talk:Caveman2009-10-08T18:45:59Z<p>Caveman: /* AJAX/JSON support in AOLserver */ removed spammer link to "buy term papers"</p>
<hr />
<div>== towards a data and authentication layer ==<br />
<br />
It is possible that similar exists elsewhere (non-OpenACS) but I enjoy framework construction anyway. Services provided:<br />
# authentication (password check)<br />
# sequences<br />
# data layer<br />
<br />
----<br />
<br />
Authentication/Authorization config (nsz):<br />
<pre><br />
# config: "/security/password/expression"<br />
# {::sha1::hmac [lindex $args 1] [lindex $args 0]}<br />
# config: "/security/password/query"<br />
# {select password, salt from users where name=[ns_dbquotevalue [lindex $args 0]]}<br />
# config: "/security/salt/length" "64"<br />
# config: "/security/salt/dictionary" "0123456789abcdefghijkl..."<br />
</pre><br />
<br />
Basically the "expression" is used in a function, '''nsz_password''' to format a given clear-text password (varargs "args" to allow additional arguments to the function). The first argument is always the password.<br />
<br />
The "query" is executed as part of password-based authentication. The form handler reaches '''nsz_auth "myname" "mypassword"''' and the query is executed using the input list "myname". All row data beyond the first column, which must always be the password, is appended to the input password "mypassword" to produce the hash/salted/hash input "xpassword". This input "xpassword" is compared with the result of the returned value for the first column from the database query. If there is a match, password authentication succeeds for the user.<br />
<br />
Examples:<br />
<pre><br />
nsz_auth "sam" "correctpassword"<br />
# Query returns "sadf8vcx8vxasd7f7...","asduf7z6dfa..."<br />
# Expression eval for input passes "correctpassword","asduf7z6dfa..." and returns "sadf8vcx8vxasd7f7..."<br />
# Return value matches query<br />
# nsz_auth returns "sam"<br />
<br />
nsz_auth "sam" "badpassword"<br />
# Query returns "sadf8vcx8vxasd7f7...","asduf7z6dfa..."<br />
# Expression eval for input passes "badpassword","asduf7z6dfa..." and returns "yyzkfosd232cx7c..."<br />
# Return value does not match query<br />
# nsz_auth raises error "bad password"<br />
</pre><br />
<br />
Different configurations could use simple clear-text passwords, no salt, etc, simply by changing their configuration:<br />
<pre><br />
# config: "nsz/security/password/expression"<br />
# {lindex $args 0}<br />
# config: "nsz/security/password/query"<br />
# {select password from users where name=[ns_dbquotevalue [lindex $args 0]]}<br />
</pre><br />
<br />
The above would be the default configuration. For salt, the default would be size of 8 and dictionary of alphanumerics.<br />
<br />
Function '''nsz_salt''' can take 0, 1, or 2 arguments and returns the generated salt. The first argument is the length of the salt, defaults to config value. The second argument is the dictionary for the salt, default to config value.<br />
<br />
'''Question:''' How to make "users" table configurable? What about configuring which database pool to use? What about multiple authentication realms?<br />
<br />
----<br />
<br />
Sequences configuration should be as simple as specifying the database pool to use (default by default), the name of the sequence table, the size of the sequence chunk to claim when the local cache runs out of sequence numbers, and the number of retries before error during chunk claim. It could however be more complex, to specify the column names for the "name" and "value" of the sequence.<br />
<br />
Config:<br />
<pre><br />
# config: "nso/sequence/default/poolname" (default by default)<br />
# config: "nso/sequence/default/size" "100"<br />
# config: "nso/sequence/default/retry" "5"<br />
# config: "nso/sequence/default/table" "sequences_table"<br />
# config: "nso/sequence/default/name" "name_field"<br />
# config: "nso/sequence/default/value" "value_field"<br />
</pre><br />
<br />
Sequence defaults could be over-written per-sequence in similar fashion.<br />
<br />
Example usage:<br />
<pre><br />
set nextId [nso_sequence next "my_seq_name"]<br />
# returns 53 or error if fail<br />
</pre><br />
<br />
The function '''nso_sequence''' would thread-safe return the next sequence number it had available in its local nsv data, or if not available, claim the next chunk of 100 sequences numbers from the database:<br />
<pre><br />
# select value_field from sequences_table where name_field='my_seq_name'<br />
# result is 125, attempt to claim 100 values<br />
# update cave_sequences set value=225 where name_field='my_seq_name' and value_field=125<br />
</pre><br />
<br />
This would be retried up to ''5'' times.<br />
<br />
----<br />
<br />
Data layer notes:<br />
<br />
Config would map names like "users" to database pools and table names. Default would be default database pool and identity table name.<br />
<br />
Example usage:<br />
<pre><br />
# set nssValues [ns_set create]<br />
# ns_set update $nssValues "name" "sam"<br />
# ns_set update $nssValues "password" "mypassword"<br />
# ns_set put $nssValues "mail" "sam@caveman.org"<br />
# set nssUserKey [nso_row create "users" $nssValues]<br />
# set nssNewValues [ns_set create]<br />
# ns_set put $nssNewValues "mail" "samuelmb@gmail.com"<br />
# nso_row update "users" $nssUserKey $nssNewValues<br />
</pre><br />
<br />
Using ns_set instead of a model type-checking "nso_set" at least for now for simplicity and it would be the simple case.<br />
<br />
Additional config allows for data transforms:<br />
<pre><br />
# multi stage of filters and expressions:<br />
#<br />
# stage 0: accept-data-filter<br />
# e.g. "require a password is not null"<br />
# e.g. "require this integer be above zero"<br />
# e.g. "require id not be set"<br />
#<br />
# stage 1: transform-data-filter<br />
# config: expressions to apply to row:<br />
# e.g. "generate a salt"<br />
# ns_set update $nssData "salt" [nsz_salt]<br />
# e.g. "transform the password"<br />
# ns_set update $nssData "password" [nsz_password [ns_set get $nssData "password"] [ns_set get $nssData "salt"]]<br />
# e.g. "generate the next id from sequence"<br />
# ns_set update $nssData "id" [nso_sequence next "my_seq_name"]<br />
#<br />
# stage 2: veto-data-filter?<br />
#<br />
# allow multiple "inheritance" of data rules? or just defining rules that<br />
# can be referenced by multiple tables?<br />
</pre><br />
<br />
''very draft state''<br />
<br />
== useful links ==<br />
[http://philip.greenspun.com/doc/ philip.greenspun.com/doc/]<br />
<br />
[http://philip.greenspun.com/doc/data-pipeline data-pipeline]<br />
<br />
== AJAX/JSON support in AOLserver ==<br />
<br />
# HTTP request hits AOLserver, returns HTML including JavaScript with AJAX (or JSON-RPC, whatever) features.<br />
# Client interacts with rendered HTML application, resulting in AJAX calls to AOLserver.<br />
# AOLserver handles the AJAX calls and responds.<br />
# Client potentially modified by result of AJAX call without reload.<br />
<br />
Use cases:<br />
# Rate something and store the rating without reload of page.<br />
# Stateful drag and drop of tiles (shopping cart, wish list).<br />
# Background saving of application state (e.g. word processor, calendar, etc) without page reload.<br />
# Reload portions of the view (e.g. portlet) without reloading the whole page. E.g. stock tickers, chat windows, log viewers, etc.<br />
# Add/remove item from cart statefully without reload of page.<br />
# Recalculate shopping cart prices/totals without reload of page.<br />
<br />
Benefits:<br />
# Allows "Web 2.0" sites such as Digg and Gmail to be run on massively scalable AOLserver platform.<br />
# It's an itch. We scratch these things.<br />
<br />
Links:<br />
* [http://www.writely.com/ writely -- the web word processor]<br />
* [http://www.digg.com/spy digg spy -- show console data e.g. log, recent searches, monitoring, stocks, etc]<br />
* [http://www.kiko.com/ kiko -- online calendar]<br />
* [http://mail.google.com/ google mail]<br />
* [http://maps.google.com/ google maps]<br />
* [http://www.crockford.com/javascript/ javascript link collection]<br />
* [http://en.wikipedia.org/wiki/AJAX wikipedia article on AJAX]<br />
* [http://rajshekhar.net/blog/archives/85-Rasmus-30-second-AJAX-Tutorial.html 30 second intro to AJAX]</div>Cavemanhttps://panoptic.com/mediawiki/aolserver/index.php?title=User_talk:Caveman&diff=5404User talk:Caveman2009-10-08T18:45:24Z<p>Caveman: /* useful links */ removed spammer links</p>
<hr />
<div>== towards a data and authentication layer ==<br />
<br />
It is possible that similar exists elsewhere (non-OpenACS) but I enjoy framework construction anyway. Services provided:<br />
# authentication (password check)<br />
# sequences<br />
# data layer<br />
<br />
----<br />
<br />
Authentication/Authorization config (nsz):<br />
<pre><br />
# config: "/security/password/expression"<br />
# {::sha1::hmac [lindex $args 1] [lindex $args 0]}<br />
# config: "/security/password/query"<br />
# {select password, salt from users where name=[ns_dbquotevalue [lindex $args 0]]}<br />
# config: "/security/salt/length" "64"<br />
# config: "/security/salt/dictionary" "0123456789abcdefghijkl..."<br />
</pre><br />
<br />
Basically the "expression" is used in a function, '''nsz_password''' to format a given clear-text password (varargs "args" to allow additional arguments to the function). The first argument is always the password.<br />
<br />
The "query" is executed as part of password-based authentication. The form handler reaches '''nsz_auth "myname" "mypassword"''' and the query is executed using the input list "myname". All row data beyond the first column, which must always be the password, is appended to the input password "mypassword" to produce the hash/salted/hash input "xpassword". This input "xpassword" is compared with the result of the returned value for the first column from the database query. If there is a match, password authentication succeeds for the user.<br />
<br />
Examples:<br />
<pre><br />
nsz_auth "sam" "correctpassword"<br />
# Query returns "sadf8vcx8vxasd7f7...","asduf7z6dfa..."<br />
# Expression eval for input passes "correctpassword","asduf7z6dfa..." and returns "sadf8vcx8vxasd7f7..."<br />
# Return value matches query<br />
# nsz_auth returns "sam"<br />
<br />
nsz_auth "sam" "badpassword"<br />
# Query returns "sadf8vcx8vxasd7f7...","asduf7z6dfa..."<br />
# Expression eval for input passes "badpassword","asduf7z6dfa..." and returns "yyzkfosd232cx7c..."<br />
# Return value does not match query<br />
# nsz_auth raises error "bad password"<br />
</pre><br />
<br />
Different configurations could use simple clear-text passwords, no salt, etc, simply by changing their configuration:<br />
<pre><br />
# config: "nsz/security/password/expression"<br />
# {lindex $args 0}<br />
# config: "nsz/security/password/query"<br />
# {select password from users where name=[ns_dbquotevalue [lindex $args 0]]}<br />
</pre><br />
<br />
The above would be the default configuration. For salt, the default would be size of 8 and dictionary of alphanumerics.<br />
<br />
Function '''nsz_salt''' can take 0, 1, or 2 arguments and returns the generated salt. The first argument is the length of the salt, defaults to config value. The second argument is the dictionary for the salt, default to config value.<br />
<br />
'''Question:''' How to make "users" table configurable? What about configuring which database pool to use? What about multiple authentication realms?<br />
<br />
----<br />
<br />
Sequences configuration should be as simple as specifying the database pool to use (default by default), the name of the sequence table, the size of the sequence chunk to claim when the local cache runs out of sequence numbers, and the number of retries before error during chunk claim. It could however be more complex, to specify the column names for the "name" and "value" of the sequence.<br />
<br />
Config:<br />
<pre><br />
# config: "nso/sequence/default/poolname" (default by default)<br />
# config: "nso/sequence/default/size" "100"<br />
# config: "nso/sequence/default/retry" "5"<br />
# config: "nso/sequence/default/table" "sequences_table"<br />
# config: "nso/sequence/default/name" "name_field"<br />
# config: "nso/sequence/default/value" "value_field"<br />
</pre><br />
<br />
Sequence defaults could be over-written per-sequence in similar fashion.<br />
<br />
Example usage:<br />
<pre><br />
set nextId [nso_sequence next "my_seq_name"]<br />
# returns 53 or error if fail<br />
</pre><br />
<br />
The function '''nso_sequence''' would thread-safe return the next sequence number it had available in its local nsv data, or if not available, claim the next chunk of 100 sequences numbers from the database:<br />
<pre><br />
# select value_field from sequences_table where name_field='my_seq_name'<br />
# result is 125, attempt to claim 100 values<br />
# update cave_sequences set value=225 where name_field='my_seq_name' and value_field=125<br />
</pre><br />
<br />
This would be retried up to ''5'' times.<br />
<br />
----<br />
<br />
Data layer notes:<br />
<br />
Config would map names like "users" to database pools and table names. Default would be default database pool and identity table name.<br />
<br />
Example usage:<br />
<pre><br />
# set nssValues [ns_set create]<br />
# ns_set update $nssValues "name" "sam"<br />
# ns_set update $nssValues "password" "mypassword"<br />
# ns_set put $nssValues "mail" "sam@caveman.org"<br />
# set nssUserKey [nso_row create "users" $nssValues]<br />
# set nssNewValues [ns_set create]<br />
# ns_set put $nssNewValues "mail" "samuelmb@gmail.com"<br />
# nso_row update "users" $nssUserKey $nssNewValues<br />
</pre><br />
<br />
Using ns_set instead of a model type-checking "nso_set" at least for now for simplicity and it would be the simple case.<br />
<br />
Additional config allows for data transforms:<br />
<pre><br />
# multi stage of filters and expressions:<br />
#<br />
# stage 0: accept-data-filter<br />
# e.g. "require a password is not null"<br />
# e.g. "require this integer be above zero"<br />
# e.g. "require id not be set"<br />
#<br />
# stage 1: transform-data-filter<br />
# config: expressions to apply to row:<br />
# e.g. "generate a salt"<br />
# ns_set update $nssData "salt" [nsz_salt]<br />
# e.g. "transform the password"<br />
# ns_set update $nssData "password" [nsz_password [ns_set get $nssData "password"] [ns_set get $nssData "salt"]]<br />
# e.g. "generate the next id from sequence"<br />
# ns_set update $nssData "id" [nso_sequence next "my_seq_name"]<br />
#<br />
# stage 2: veto-data-filter?<br />
#<br />
# allow multiple "inheritance" of data rules? or just defining rules that<br />
# can be referenced by multiple tables?<br />
</pre><br />
<br />
''very draft state''<br />
<br />
== useful links ==<br />
[http://philip.greenspun.com/doc/ philip.greenspun.com/doc/]<br />
<br />
[http://philip.greenspun.com/doc/data-pipeline data-pipeline]<br />
<br />
== AJAX/JSON support in AOLserver ==<br />
<br />
# HTTP request hits AOLserver, returns HTML including JavaScript with AJAX (or JSON-RPC, whatever) features.<br />
# Client interacts with rendered HTML application, resulting in AJAX calls to AOLserver.<br />
# AOLserver handles the AJAX calls and responds.<br />
# Client potentially modified by result of AJAX call without reload.<br />
<br />
Use cases:<br />
# Rate something and store the rating without reload of page.<br />
# Stateful drag and drop of tiles (shopping cart, wish list).<br />
# Background saving of application state (e.g. word processor, calendar, etc) without page reload.<br />
# Reload portions of the view (e.g. portlet) without reloading the whole page. E.g. stock tickers, chat windows, log viewers, etc.<br />
# Add/remove item from cart statefully without reload of page.<br />
# Recalculate shopping cart prices/totals without reload of page.<br />
<br />
Benefits:<br />
# Allows "Web 2.0" sites such as Digg and Gmail to be run on massively scalable AOLserver platform.<br />
# It's an itch. We scratch these things.<br />
<br />
Links:<br />
* [http://www.term-paper-research.com/ buy term papers]<br />
* [http://www.writely.com/ writely -- the web word processor]<br />
* [http://www.digg.com/spy digg spy -- show console data e.g. log, recent searches, monitoring, stocks, etc]<br />
* [http://www.kiko.com/ kiko -- online calendar]<br />
* [http://mail.google.com/ google mail]<br />
* [http://maps.google.com/ google maps]<br />
* [http://www.crockford.com/javascript/ javascript link collection]<br />
* [http://en.wikipedia.org/wiki/AJAX wikipedia article on AJAX]<br />
* [http://rajshekhar.net/blog/archives/85-Rasmus-30-second-AJAX-Tutorial.html 30 second intro to AJAX]</div>Cavemanhttps://panoptic.com/mediawiki/aolserver/index.php?title=Ns_library&diff=4684Ns library2006-01-11T21:52:00Z<p>Caveman: </p>
<hr />
<div>Man page: http://aolserver.com/docs/tcl/ns_library.html<br />
<br />
----<br />
<br />
'''NAME'''<br />
<br />
: ns_library - Get the paths to the private and shared Tcl libraries<br />
<br />
'''SYNOPSIS'''<br />
<br />
: '''ns_library''' ''library ?module?''<br />
<br />
'''DESCRIPTION'''<br />
<br />
: This command returns the path to the private and shared Tcl libraries, optionally specifying a ''module'' as well.<br />
''library'' must either be "private" or "shared". The private library is the same as what's returned from [[ns_info]] '''tcllib''' as defined in the config .tcl at server start-up. The shared library is relative to the path specified by [[ns_info]] '''home''', in the "modules/tcl" subdirectory.<br />
<br />
: The optional ''module'' is simply concatenated to the path returned from '''ns_library'''.<br />
<br />
'''EXAMPLES'''<br />
<br />
% ns_library shared<br />
/home/aolserver/modules/tcl<br />
<br />
% file join [ns_info home] modules tcl<br />
/home/aolserver/modules/tcl<br />
<br />
% ns_library private exampleModule<br />
/home/aolserver/servers/exampleServer/tcl/exampleModule<br />
<br />
% file join [ns_info tcllib] exampleModule<br />
/home/aolserver/servers/exampleServer/tcl/exampleModule<br />
<br />
'''SEE ALSO'''<br />
<br />
: [[ns_info]] '''home''', [[ns_info]] '''tcllib'''<br />
<br />
----<br />
<br />
[[Category Documentation]] - [[Category Core Tcl API]]</div>Cavemanhttps://panoptic.com/mediawiki/aolserver/index.php?title=Talk:Ns_register_proc&diff=4683Talk:Ns register proc2006-01-11T21:31:14Z<p>Caveman: getting modules to reload</p>
<hr />
<div>== getting modules to reload ==<br />
<br />
Using stock install of Debian's AOLserver package, I am trying to figure out how to get my modules to automatically reload (or even manually) without having to restart the entire server. Is this possible? If so, how?<br />
<br />
Explanation:<br />
<br />
I have a module "mymod.tcl" in "/usr/lib/aolserver4/servers/main/modules/tcl". I want to change a small bit of behavior in the module, say, correcting a typographical error. In order to get this change to be read by the server, I have to stop and then start the server. This is not desired.<br />
<br />
--[[User:Caveman|Caveman]] 16:31, 11 January 2006 (EST)</div>Cavemanhttps://panoptic.com/mediawiki/aolserver/index.php?title=User_talk:Caveman&diff=4658User talk:Caveman2006-01-01T16:05:27Z<p>Caveman: /* AJAX/JSON support in AOLserver */</p>
<hr />
<div>== towards a data and authentication layer ==<br />
<br />
It is possible that similar exists elsewhere (non-OpenACS) but I enjoy framework construction anyway. Services provided:<br />
# authentication (password check)<br />
# sequences<br />
# data layer<br />
<br />
----<br />
<br />
Authentication/Authorization config (nsz):<br />
<pre><br />
# config: "/security/password/expression"<br />
# {::sha1::hmac [lindex $args 1] [lindex $args 0]}<br />
# config: "/security/password/query"<br />
# {select password, salt from users where name=[ns_dbquotevalue [lindex $args 0]]}<br />
# config: "/security/salt/length" "64"<br />
# config: "/security/salt/dictionary" "0123456789abcdefghijkl..."<br />
</pre><br />
<br />
Basically the "expression" is used in a function, '''nsz_password''' to format a given clear-text password (varargs "args" to allow additional arguments to the function). The first argument is always the password.<br />
<br />
The "query" is executed as part of password-based authentication. The form handler reaches '''nsz_auth "myname" "mypassword"''' and the query is executed using the input list "myname". All row data beyond the first column, which must always be the password, is appended to the input password "mypassword" to produce the hash/salted/hash input "xpassword". This input "xpassword" is compared with the result of the returned value for the first column from the database query. If there is a match, password authentication succeeds for the user.<br />
<br />
Examples:<br />
<pre><br />
nsz_auth "sam" "correctpassword"<br />
# Query returns "sadf8vcx8vxasd7f7...","asduf7z6dfa..."<br />
# Expression eval for input passes "correctpassword","asduf7z6dfa..." and returns "sadf8vcx8vxasd7f7..."<br />
# Return value matches query<br />
# nsz_auth returns "sam"<br />
<br />
nsz_auth "sam" "badpassword"<br />
# Query returns "sadf8vcx8vxasd7f7...","asduf7z6dfa..."<br />
# Expression eval for input passes "badpassword","asduf7z6dfa..." and returns "yyzkfosd232cx7c..."<br />
# Return value does not match query<br />
# nsz_auth raises error "bad password"<br />
</pre><br />
<br />
Different configurations could use simple clear-text passwords, no salt, etc, simply by changing their configuration:<br />
<pre><br />
# config: "nsz/security/password/expression"<br />
# {lindex $args 0}<br />
# config: "nsz/security/password/query"<br />
# {select password from users where name=[ns_dbquotevalue [lindex $args 0]]}<br />
</pre><br />
<br />
The above would be the default configuration. For salt, the default would be size of 8 and dictionary of alphanumerics.<br />
<br />
Function '''nsz_salt''' can take 0, 1, or 2 arguments and returns the generated salt. The first argument is the length of the salt, defaults to config value. The second argument is the dictionary for the salt, default to config value.<br />
<br />
'''Question:''' How to make "users" table configurable? What about configuring which database pool to use? What about multiple authentication realms?<br />
<br />
----<br />
<br />
Sequences configuration should be as simple as specifying the database pool to use (default by default), the name of the sequence table, the size of the sequence chunk to claim when the local cache runs out of sequence numbers, and the number of retries before error during chunk claim. It could however be more complex, to specify the column names for the "name" and "value" of the sequence.<br />
<br />
Config:<br />
<pre><br />
# config: "nso/sequence/default/poolname" (default by default)<br />
# config: "nso/sequence/default/size" "100"<br />
# config: "nso/sequence/default/retry" "5"<br />
# config: "nso/sequence/default/table" "sequences_table"<br />
# config: "nso/sequence/default/name" "name_field"<br />
# config: "nso/sequence/default/value" "value_field"<br />
</pre><br />
<br />
Sequence defaults could be over-written per-sequence in similar fashion.<br />
<br />
Example usage:<br />
<pre><br />
set nextId [nso_sequence next "my_seq_name"]<br />
# returns 53 or error if fail<br />
</pre><br />
<br />
The function '''nso_sequence''' would thread-safe return the next sequence number it had available in its local nsv data, or if not available, claim the next chunk of 100 sequences numbers from the database:<br />
<pre><br />
# select value_field from sequences_table where name_field='my_seq_name'<br />
# result is 125, attempt to claim 100 values<br />
# update cave_sequences set value=225 where name_field='my_seq_name' and value_field=125<br />
</pre><br />
<br />
This would be retried up to ''5'' times.<br />
<br />
----<br />
<br />
Data layer notes:<br />
<br />
Config would map names like "users" to database pools and table names. Default would be default database pool and identity table name.<br />
<br />
Example usage:<br />
<pre><br />
# set nssValues [ns_set create]<br />
# ns_set update $nssValues "name" "sam"<br />
# ns_set update $nssValues "password" "mypassword"<br />
# ns_set put $nssValues "mail" "sam@caveman.org"<br />
# set nssUserKey [nso_row create "users" $nssValues]<br />
# set nssNewValues [ns_set create]<br />
# ns_set put $nssNewValues "mail" "samuelmb@gmail.com"<br />
# nso_row update "users" $nssUserKey $nssNewValues<br />
</pre><br />
<br />
Using ns_set instead of a model type-checking "nso_set" at least for now for simplicity and it would be the simple case.<br />
<br />
Additional config allows for data transforms:<br />
<pre><br />
# multi stage of filters and expressions:<br />
#<br />
# stage 0: accept-data-filter<br />
# e.g. "require a password is not null"<br />
# e.g. "require this integer be above zero"<br />
# e.g. "require id not be set"<br />
#<br />
# stage 1: transform-data-filter<br />
# config: expressions to apply to row:<br />
# e.g. "generate a salt"<br />
# ns_set update $nssData "salt" [nsz_salt]<br />
# e.g. "transform the password"<br />
# ns_set update $nssData "password" [nsz_password [ns_set get $nssData "password"] [ns_set get $nssData "salt"]]<br />
# e.g. "generate the next id from sequence"<br />
# ns_set update $nssData "id" [nso_sequence next "my_seq_name"]<br />
#<br />
# stage 2: veto-data-filter?<br />
#<br />
# allow multiple "inheritance" of data rules? or just defining rules that<br />
# can be referenced by multiple tables?<br />
</pre><br />
<br />
''very draft state''<br />
<br />
== useful links ==<br />
[http://philip.greenspun.com/doc/ philip.greenspun.com/doc/]<br />
[http://philip.greenspun.com/doc/data-pipeline data-pipeline]<br />
<br />
== AJAX/JSON support in AOLserver ==<br />
<br />
# HTTP request hits AOLserver, returns HTML including JavaScript with AJAX (or JSON-RPC, whatever) features.<br />
# Client interacts with rendered HTML application, resulting in AJAX calls to AOLserver.<br />
# AOLserver handles the AJAX calls and responds.<br />
# Client potentially modified by result of AJAX call without reload.<br />
<br />
Use cases:<br />
# Rate something and store the rating without reload of page.<br />
# Stateful drag and drop of tiles (shopping cart, wish list).<br />
# Background saving of application state (e.g. word processor, calendar, etc) without page reload.<br />
# Reload portions of the view (e.g. portlet) without reloading the whole page. E.g. stock tickers, chat windows, log viewers, etc.<br />
# Add/remove item from cart statefully without reload of page.<br />
# Recalculate shopping cart prices/totals without reload of page.<br />
<br />
Benefits:<br />
# Allows "Web 2.0" sites such as Digg and Gmail to be run on massively scalable AOLserver platform.<br />
# It's an itch. We scratch these things.<br />
<br />
Links:<br />
* [http://www.writely.com/ writely -- the web word processor]<br />
* [http://www.digg.com/spy digg spy -- show console data e.g. log, recent searches, monitoring, stocks, etc]<br />
* [http://www.kiko.com/ kiko -- online calendar]<br />
* [http://mail.google.com/ google mail]<br />
* [http://maps.google.com/ google maps]<br />
* [http://www.crockford.com/javascript/ javascript link collection]<br />
* [http://en.wikipedia.org/wiki/AJAX wikipedia article on AJAX]<br />
* [http://rajshekhar.net/blog/archives/85-Rasmus-30-second-AJAX-Tutorial.html 30 second intro to AJAX]</div>Cavemanhttps://panoptic.com/mediawiki/aolserver/index.php?title=User_talk:Caveman&diff=4654User talk:Caveman2005-12-25T22:17:37Z<p>Caveman: /* AJAX/JSON support in AOLserver */</p>
<hr />
<div>== towards a data and authentication layer ==<br />
<br />
It is possible that similar exists elsewhere (non-OpenACS) but I enjoy framework construction anyway. Services provided:<br />
# authentication (password check)<br />
# sequences<br />
# data layer<br />
<br />
----<br />
<br />
Authentication/Authorization config (nsz):<br />
<pre><br />
# config: "/security/password/expression"<br />
# {::sha1::hmac [lindex $args 1] [lindex $args 0]}<br />
# config: "/security/password/query"<br />
# {select password, salt from users where name=[ns_dbquotevalue [lindex $args 0]]}<br />
# config: "/security/salt/length" "64"<br />
# config: "/security/salt/dictionary" "0123456789abcdefghijkl..."<br />
</pre><br />
<br />
Basically the "expression" is used in a function, '''nsz_password''' to format a given clear-text password (varargs "args" to allow additional arguments to the function). The first argument is always the password.<br />
<br />
The "query" is executed as part of password-based authentication. The form handler reaches '''nsz_auth "myname" "mypassword"''' and the query is executed using the input list "myname". All row data beyond the first column, which must always be the password, is appended to the input password "mypassword" to produce the hash/salted/hash input "xpassword". This input "xpassword" is compared with the result of the returned value for the first column from the database query. If there is a match, password authentication succeeds for the user.<br />
<br />
Examples:<br />
<pre><br />
nsz_auth "sam" "correctpassword"<br />
# Query returns "sadf8vcx8vxasd7f7...","asduf7z6dfa..."<br />
# Expression eval for input passes "correctpassword","asduf7z6dfa..." and returns "sadf8vcx8vxasd7f7..."<br />
# Return value matches query<br />
# nsz_auth returns "sam"<br />
<br />
nsz_auth "sam" "badpassword"<br />
# Query returns "sadf8vcx8vxasd7f7...","asduf7z6dfa..."<br />
# Expression eval for input passes "badpassword","asduf7z6dfa..." and returns "yyzkfosd232cx7c..."<br />
# Return value does not match query<br />
# nsz_auth raises error "bad password"<br />
</pre><br />
<br />
Different configurations could use simple clear-text passwords, no salt, etc, simply by changing their configuration:<br />
<pre><br />
# config: "nsz/security/password/expression"<br />
# {lindex $args 0}<br />
# config: "nsz/security/password/query"<br />
# {select password from users where name=[ns_dbquotevalue [lindex $args 0]]}<br />
</pre><br />
<br />
The above would be the default configuration. For salt, the default would be size of 8 and dictionary of alphanumerics.<br />
<br />
Function '''nsz_salt''' can take 0, 1, or 2 arguments and returns the generated salt. The first argument is the length of the salt, defaults to config value. The second argument is the dictionary for the salt, default to config value.<br />
<br />
'''Question:''' How to make "users" table configurable? What about configuring which database pool to use? What about multiple authentication realms?<br />
<br />
----<br />
<br />
Sequences configuration should be as simple as specifying the database pool to use (default by default), the name of the sequence table, the size of the sequence chunk to claim when the local cache runs out of sequence numbers, and the number of retries before error during chunk claim. It could however be more complex, to specify the column names for the "name" and "value" of the sequence.<br />
<br />
Config:<br />
<pre><br />
# config: "nso/sequence/default/poolname" (default by default)<br />
# config: "nso/sequence/default/size" "100"<br />
# config: "nso/sequence/default/retry" "5"<br />
# config: "nso/sequence/default/table" "sequences_table"<br />
# config: "nso/sequence/default/name" "name_field"<br />
# config: "nso/sequence/default/value" "value_field"<br />
</pre><br />
<br />
Sequence defaults could be over-written per-sequence in similar fashion.<br />
<br />
Example usage:<br />
<pre><br />
set nextId [nso_sequence next "my_seq_name"]<br />
# returns 53 or error if fail<br />
</pre><br />
<br />
The function '''nso_sequence''' would thread-safe return the next sequence number it had available in its local nsv data, or if not available, claim the next chunk of 100 sequences numbers from the database:<br />
<pre><br />
# select value_field from sequences_table where name_field='my_seq_name'<br />
# result is 125, attempt to claim 100 values<br />
# update cave_sequences set value=225 where name_field='my_seq_name' and value_field=125<br />
</pre><br />
<br />
This would be retried up to ''5'' times.<br />
<br />
----<br />
<br />
Data layer notes:<br />
<br />
Config would map names like "users" to database pools and table names. Default would be default database pool and identity table name.<br />
<br />
Example usage:<br />
<pre><br />
# set nssValues [ns_set create]<br />
# ns_set update $nssValues "name" "sam"<br />
# ns_set update $nssValues "password" "mypassword"<br />
# ns_set put $nssValues "mail" "sam@caveman.org"<br />
# set nssUserKey [nso_row create "users" $nssValues]<br />
# set nssNewValues [ns_set create]<br />
# ns_set put $nssNewValues "mail" "samuelmb@gmail.com"<br />
# nso_row update "users" $nssUserKey $nssNewValues<br />
</pre><br />
<br />
Using ns_set instead of a model type-checking "nso_set" at least for now for simplicity and it would be the simple case.<br />
<br />
Additional config allows for data transforms:<br />
<pre><br />
# multi stage of filters and expressions:<br />
#<br />
# stage 0: accept-data-filter<br />
# e.g. "require a password is not null"<br />
# e.g. "require this integer be above zero"<br />
# e.g. "require id not be set"<br />
#<br />
# stage 1: transform-data-filter<br />
# config: expressions to apply to row:<br />
# e.g. "generate a salt"<br />
# ns_set update $nssData "salt" [nsz_salt]<br />
# e.g. "transform the password"<br />
# ns_set update $nssData "password" [nsz_password [ns_set get $nssData "password"] [ns_set get $nssData "salt"]]<br />
# e.g. "generate the next id from sequence"<br />
# ns_set update $nssData "id" [nso_sequence next "my_seq_name"]<br />
#<br />
# stage 2: veto-data-filter?<br />
#<br />
# allow multiple "inheritance" of data rules? or just defining rules that<br />
# can be referenced by multiple tables?<br />
</pre><br />
<br />
''very draft state''<br />
<br />
== useful links ==<br />
[http://philip.greenspun.com/doc/ philip.greenspun.com/doc/]<br />
[http://philip.greenspun.com/doc/data-pipeline data-pipeline]<br />
<br />
== AJAX/JSON support in AOLserver ==<br />
<br />
# HTTP request hits AOLserver, returns HTML including JavaScript with AJAX (or JSON-RPC, whatever) features.<br />
# Client interacts with rendered HTML application, resulting in AJAX calls to AOLserver.<br />
# AOLserver handles the AJAX calls and responds.<br />
# Client potentially modified by result of AJAX call without reload.<br />
<br />
Use cases:<br />
# Rate something and store the rating without reload of page.<br />
# Stateful drag and drop of tiles (shopping cart, wish list).<br />
# Background saving of application state (e.g. word processor, calendar, etc) without page reload.<br />
# Reload portions of the view (e.g. portlet) without reloading the whole page. E.g. stock tickers, chat windows, log viewers, etc.<br />
# Add/remove item from cart statefully without reload of page.<br />
# Recalculate shopping cart prices/totals without reload of page.<br />
<br />
Benefits:<br />
# Allows "Web 2.0" sites such as Digg and Gmail to be run on massively scalable AOLserver platform.<br />
# It's an itch. We scratch these things.<br />
<br />
Links:<br />
* [http://www.writely.com/ writely -- the web word processor]<br />
* [http://www.digg.com/spy digg spy -- show console data e.g. log, recent searches, monitoring, stocks, etc]<br />
* [http://www.kiko.com/ kiko -- online calendar]<br />
* [http://mail.google.com/ google mail]<br />
* [http://maps.google.com/ google maps]<br />
* [http://www.crockford.com/javascript/ javascript link collection]<br />
* [http://en.wikipedia.org/wiki/AJAX wikipedia article on AJAX]</div>Cavemanhttps://panoptic.com/mediawiki/aolserver/index.php?title=User_talk:Caveman&diff=4653User talk:Caveman2005-12-25T22:16:41Z<p>Caveman: AJAX/JSON support in AOLserver</p>
<hr />
<div>== towards a data and authentication layer ==<br />
<br />
It is possible that similar exists elsewhere (non-OpenACS) but I enjoy framework construction anyway. Services provided:<br />
# authentication (password check)<br />
# sequences<br />
# data layer<br />
<br />
----<br />
<br />
Authentication/Authorization config (nsz):<br />
<pre><br />
# config: "/security/password/expression"<br />
# {::sha1::hmac [lindex $args 1] [lindex $args 0]}<br />
# config: "/security/password/query"<br />
# {select password, salt from users where name=[ns_dbquotevalue [lindex $args 0]]}<br />
# config: "/security/salt/length" "64"<br />
# config: "/security/salt/dictionary" "0123456789abcdefghijkl..."<br />
</pre><br />
<br />
Basically the "expression" is used in a function, '''nsz_password''' to format a given clear-text password (varargs "args" to allow additional arguments to the function). The first argument is always the password.<br />
<br />
The "query" is executed as part of password-based authentication. The form handler reaches '''nsz_auth "myname" "mypassword"''' and the query is executed using the input list "myname". All row data beyond the first column, which must always be the password, is appended to the input password "mypassword" to produce the hash/salted/hash input "xpassword". This input "xpassword" is compared with the result of the returned value for the first column from the database query. If there is a match, password authentication succeeds for the user.<br />
<br />
Examples:<br />
<pre><br />
nsz_auth "sam" "correctpassword"<br />
# Query returns "sadf8vcx8vxasd7f7...","asduf7z6dfa..."<br />
# Expression eval for input passes "correctpassword","asduf7z6dfa..." and returns "sadf8vcx8vxasd7f7..."<br />
# Return value matches query<br />
# nsz_auth returns "sam"<br />
<br />
nsz_auth "sam" "badpassword"<br />
# Query returns "sadf8vcx8vxasd7f7...","asduf7z6dfa..."<br />
# Expression eval for input passes "badpassword","asduf7z6dfa..." and returns "yyzkfosd232cx7c..."<br />
# Return value does not match query<br />
# nsz_auth raises error "bad password"<br />
</pre><br />
<br />
Different configurations could use simple clear-text passwords, no salt, etc, simply by changing their configuration:<br />
<pre><br />
# config: "nsz/security/password/expression"<br />
# {lindex $args 0}<br />
# config: "nsz/security/password/query"<br />
# {select password from users where name=[ns_dbquotevalue [lindex $args 0]]}<br />
</pre><br />
<br />
The above would be the default configuration. For salt, the default would be size of 8 and dictionary of alphanumerics.<br />
<br />
Function '''nsz_salt''' can take 0, 1, or 2 arguments and returns the generated salt. The first argument is the length of the salt, defaults to config value. The second argument is the dictionary for the salt, default to config value.<br />
<br />
'''Question:''' How to make "users" table configurable? What about configuring which database pool to use? What about multiple authentication realms?<br />
<br />
----<br />
<br />
Sequences configuration should be as simple as specifying the database pool to use (default by default), the name of the sequence table, the size of the sequence chunk to claim when the local cache runs out of sequence numbers, and the number of retries before error during chunk claim. It could however be more complex, to specify the column names for the "name" and "value" of the sequence.<br />
<br />
Config:<br />
<pre><br />
# config: "nso/sequence/default/poolname" (default by default)<br />
# config: "nso/sequence/default/size" "100"<br />
# config: "nso/sequence/default/retry" "5"<br />
# config: "nso/sequence/default/table" "sequences_table"<br />
# config: "nso/sequence/default/name" "name_field"<br />
# config: "nso/sequence/default/value" "value_field"<br />
</pre><br />
<br />
Sequence defaults could be over-written per-sequence in similar fashion.<br />
<br />
Example usage:<br />
<pre><br />
set nextId [nso_sequence next "my_seq_name"]<br />
# returns 53 or error if fail<br />
</pre><br />
<br />
The function '''nso_sequence''' would thread-safe return the next sequence number it had available in its local nsv data, or if not available, claim the next chunk of 100 sequences numbers from the database:<br />
<pre><br />
# select value_field from sequences_table where name_field='my_seq_name'<br />
# result is 125, attempt to claim 100 values<br />
# update cave_sequences set value=225 where name_field='my_seq_name' and value_field=125<br />
</pre><br />
<br />
This would be retried up to ''5'' times.<br />
<br />
----<br />
<br />
Data layer notes:<br />
<br />
Config would map names like "users" to database pools and table names. Default would be default database pool and identity table name.<br />
<br />
Example usage:<br />
<pre><br />
# set nssValues [ns_set create]<br />
# ns_set update $nssValues "name" "sam"<br />
# ns_set update $nssValues "password" "mypassword"<br />
# ns_set put $nssValues "mail" "sam@caveman.org"<br />
# set nssUserKey [nso_row create "users" $nssValues]<br />
# set nssNewValues [ns_set create]<br />
# ns_set put $nssNewValues "mail" "samuelmb@gmail.com"<br />
# nso_row update "users" $nssUserKey $nssNewValues<br />
</pre><br />
<br />
Using ns_set instead of a model type-checking "nso_set" at least for now for simplicity and it would be the simple case.<br />
<br />
Additional config allows for data transforms:<br />
<pre><br />
# multi stage of filters and expressions:<br />
#<br />
# stage 0: accept-data-filter<br />
# e.g. "require a password is not null"<br />
# e.g. "require this integer be above zero"<br />
# e.g. "require id not be set"<br />
#<br />
# stage 1: transform-data-filter<br />
# config: expressions to apply to row:<br />
# e.g. "generate a salt"<br />
# ns_set update $nssData "salt" [nsz_salt]<br />
# e.g. "transform the password"<br />
# ns_set update $nssData "password" [nsz_password [ns_set get $nssData "password"] [ns_set get $nssData "salt"]]<br />
# e.g. "generate the next id from sequence"<br />
# ns_set update $nssData "id" [nso_sequence next "my_seq_name"]<br />
#<br />
# stage 2: veto-data-filter?<br />
#<br />
# allow multiple "inheritance" of data rules? or just defining rules that<br />
# can be referenced by multiple tables?<br />
</pre><br />
<br />
''very draft state''<br />
<br />
== useful links ==<br />
[http://philip.greenspun.com/doc/ philip.greenspun.com/doc/]<br />
[http://philip.greenspun.com/doc/data-pipeline data-pipeline]<br />
<br />
== AJAX/JSON support in AOLserver ==<br />
<br />
1. HTTP request hits AOLserver, returns HTML including JavaScript with AJAX (or JSON-RPC, whatever) features.<br />
2. Client interacts with rendered HTML application, resulting in AJAX calls to AOLserver.<br />
3. AOLserver handles the AJAX calls and responds.<br />
4. Client potentially modified by result of AJAX call without reload.<br />
<br />
Use cases:<br />
1. Rate something and store the rating without reload of page.<br />
2. Stateful drag and drop of tiles (shopping cart, wish list).<br />
3. Background saving of application state (e.g. word processor, calendar, etc) without page reload.<br />
4. Reload portions of the view (e.g. portlet) without reloading the whole page. E.g. stock tickers, chat windows, log viewers, etc.<br />
5. Add/remove item from cart statefully without reload of page.<br />
6. Recalculate shopping cart prices/totals without reload of page.<br />
<br />
Benefits:<br />
1. Allows "Web 2.0" sites such as Digg and Gmail to be run on massively scalable AOLserver platform.<br />
2. It's an itch. We scratch these things.<br />
<br />
Links:<br />
[http://www.writely.com/ writely -- the web word processor]<br />
[http://www.digg.com/spy digg spy -- show console data e.g. log, recent searches, monitoring, stocks, etc]<br />
[http://www.kiko.com/ kiko -- online calendar]<br />
[http://mail.google.com/ google mail]<br />
[http://maps.google.com/ google maps]<br />
[http://www.crockford.com/javascript/ javascript link collection]<br />
[http://en.wikipedia.org/wiki/AJAX wikipedia article on AJAX]</div>Cavemanhttps://panoptic.com/mediawiki/aolserver/index.php?title=User:Caveman&diff=4652User:Caveman2005-12-25T22:06:07Z<p>Caveman: </p>
<hr />
<div>[mailto:sam@caveman.org Samuel Montgomery-Blinn]<br />
<br />
An off-and-on hobbyist user of Aolserver from 3.x days. Never been an OpenACS fan, hope that doesn't get me into trouble someday. My Aolserver runs on Debian 3.1 using the aolserver4-* binary packages, so I thank the maintainers for their time and effort.<br />
<br />
'''Current primary AOLserver interest:'''<br />
<br />
"Web 2.0" buzzword tinkering with AOLserver: AJAX primarily. Atom/RSS, "Web Services".<br />
<br />
'''Current seconday AOLserver interests:'''<br />
<br />
Best Practices on cookie management and session management with AOLServer<br />
<br />
Best Pratcices for identity management and authorization model AOLServer<br />
<br />
Tinkering with a standardised phpinfo() alike command: [http://caveman.org/info/]<br />
<br />
Blogging/discussion software, especially usefully multi-user.<br />
<br />
SVG graphics generation.<br />
<br />
Application model and management.<br />
<br />
nsdbeans data layer (similar to Java's EJB, or Python's SQLObject).<br />
<br />
SOAP conversation with directi's reseller server [http://manage.directi.com/kb/servlet/KBServlet/cat106.html]<br />
<br />
...<br />
<br />
'''Current 'real' work:'''<br />
<br />
A lot of JACL/TCL scripting in the test automation world for "nameless big software company". WebSphere includes a JACL administrative shell that is quite useful for scripting all kinds of configuration and test activity for J2EE applications.</div>Cavemanhttps://panoptic.com/mediawiki/aolserver/index.php?title=User_talk:Caveman&diff=4644User talk:Caveman2005-12-14T22:57:19Z<p>Caveman: corrected use of ns_dbquotevalue</p>
<hr />
<div>== towards a data and authentication layer ==<br />
<br />
It is possible that similar exists elsewhere (non-OpenACS) but I enjoy framework construction anyway. Services provided:<br />
# authentication (password check)<br />
# sequences<br />
# data layer<br />
<br />
----<br />
<br />
Authentication/Authorization config (nsz):<br />
<pre><br />
# config: "/security/password/expression"<br />
# {::sha1::hmac [lindex $args 1] [lindex $args 0]}<br />
# config: "/security/password/query"<br />
# {select password, salt from users where name=[ns_dbquotevalue [lindex $args 0]]}<br />
# config: "/security/salt/length" "64"<br />
# config: "/security/salt/dictionary" "0123456789abcdefghijkl..."<br />
</pre><br />
<br />
Basically the "expression" is used in a function, '''nsz_password''' to format a given clear-text password (varargs "args" to allow additional arguments to the function). The first argument is always the password.<br />
<br />
The "query" is executed as part of password-based authentication. The form handler reaches '''nsz_auth "myname" "mypassword"''' and the query is executed using the input list "myname". All row data beyond the first column, which must always be the password, is appended to the input password "mypassword" to produce the hash/salted/hash input "xpassword". This input "xpassword" is compared with the result of the returned value for the first column from the database query. If there is a match, password authentication succeeds for the user.<br />
<br />
Examples:<br />
<pre><br />
nsz_auth "sam" "correctpassword"<br />
# Query returns "sadf8vcx8vxasd7f7...","asduf7z6dfa..."<br />
# Expression eval for input passes "correctpassword","asduf7z6dfa..." and returns "sadf8vcx8vxasd7f7..."<br />
# Return value matches query<br />
# nsz_auth returns "sam"<br />
<br />
nsz_auth "sam" "badpassword"<br />
# Query returns "sadf8vcx8vxasd7f7...","asduf7z6dfa..."<br />
# Expression eval for input passes "badpassword","asduf7z6dfa..." and returns "yyzkfosd232cx7c..."<br />
# Return value does not match query<br />
# nsz_auth raises error "bad password"<br />
</pre><br />
<br />
Different configurations could use simple clear-text passwords, no salt, etc, simply by changing their configuration:<br />
<pre><br />
# config: "nsz/security/password/expression"<br />
# {lindex $args 0}<br />
# config: "nsz/security/password/query"<br />
# {select password from users where name=[ns_dbquotevalue [lindex $args 0]]}<br />
</pre><br />
<br />
The above would be the default configuration. For salt, the default would be size of 8 and dictionary of alphanumerics.<br />
<br />
Function '''nsz_salt''' can take 0, 1, or 2 arguments and returns the generated salt. The first argument is the length of the salt, defaults to config value. The second argument is the dictionary for the salt, default to config value.<br />
<br />
'''Question:''' How to make "users" table configurable? What about configuring which database pool to use? What about multiple authentication realms?<br />
<br />
----<br />
<br />
Sequences configuration should be as simple as specifying the database pool to use (default by default), the name of the sequence table, the size of the sequence chunk to claim when the local cache runs out of sequence numbers, and the number of retries before error during chunk claim. It could however be more complex, to specify the column names for the "name" and "value" of the sequence.<br />
<br />
Config:<br />
<pre><br />
# config: "nso/sequence/default/poolname" (default by default)<br />
# config: "nso/sequence/default/size" "100"<br />
# config: "nso/sequence/default/retry" "5"<br />
# config: "nso/sequence/default/table" "sequences_table"<br />
# config: "nso/sequence/default/name" "name_field"<br />
# config: "nso/sequence/default/value" "value_field"<br />
</pre><br />
<br />
Sequence defaults could be over-written per-sequence in similar fashion.<br />
<br />
Example usage:<br />
<pre><br />
set nextId [nso_sequence next "my_seq_name"]<br />
# returns 53 or error if fail<br />
</pre><br />
<br />
The function '''nso_sequence''' would thread-safe return the next sequence number it had available in its local nsv data, or if not available, claim the next chunk of 100 sequences numbers from the database:<br />
<pre><br />
# select value_field from sequences_table where name_field='my_seq_name'<br />
# result is 125, attempt to claim 100 values<br />
# update cave_sequences set value=225 where name_field='my_seq_name' and value_field=125<br />
</pre><br />
<br />
This would be retried up to ''5'' times.<br />
<br />
----<br />
<br />
Data layer notes:<br />
<br />
Config would map names like "users" to database pools and table names. Default would be default database pool and identity table name.<br />
<br />
Example usage:<br />
<pre><br />
# set nssValues [ns_set create]<br />
# ns_set update $nssValues "name" "sam"<br />
# ns_set update $nssValues "password" "mypassword"<br />
# ns_set put $nssValues "mail" "sam@caveman.org"<br />
# set nssUserKey [nso_row create "users" $nssValues]<br />
# set nssNewValues [ns_set create]<br />
# ns_set put $nssNewValues "mail" "samuelmb@gmail.com"<br />
# nso_row update "users" $nssUserKey $nssNewValues<br />
</pre><br />
<br />
Using ns_set instead of a model type-checking "nso_set" at least for now for simplicity and it would be the simple case.<br />
<br />
Additional config allows for data transforms:<br />
<pre><br />
# multi stage of filters and expressions:<br />
#<br />
# stage 0: accept-data-filter<br />
# e.g. "require a password is not null"<br />
# e.g. "require this integer be above zero"<br />
# e.g. "require id not be set"<br />
#<br />
# stage 1: transform-data-filter<br />
# config: expressions to apply to row:<br />
# e.g. "generate a salt"<br />
# ns_set update $nssData "salt" [nsz_salt]<br />
# e.g. "transform the password"<br />
# ns_set update $nssData "password" [nsz_password [ns_set get $nssData "password"] [ns_set get $nssData "salt"]]<br />
# e.g. "generate the next id from sequence"<br />
# ns_set update $nssData "id" [nso_sequence next "my_seq_name"]<br />
#<br />
# stage 2: veto-data-filter?<br />
#<br />
# allow multiple "inheritance" of data rules? or just defining rules that<br />
# can be referenced by multiple tables?<br />
</pre><br />
<br />
''very draft state''<br />
<br />
== useful links ==<br />
[http://philip.greenspun.com/doc/ philip.greenspun.com/doc/]<br />
[http://philip.greenspun.com/doc/data-pipeline data-pipeline]</div>Cavemanhttps://panoptic.com/mediawiki/aolserver/index.php?title=User_talk:Caveman&diff=4643User talk:Caveman2005-12-14T21:53:13Z<p>Caveman: </p>
<hr />
<div>== towards a data and authentication layer ==<br />
<br />
It is possible that similar exists elsewhere (non-OpenACS) but I enjoy framework construction anyway. Services provided:<br />
# authentication (password check)<br />
# sequences<br />
# data layer<br />
<br />
----<br />
<br />
Authentication/Authorization config (nsz):<br />
<pre><br />
# config: "/security/password/expression"<br />
# {::sha1::hmac [lindex $args 1] [lindex $args 0]}<br />
# config: "/security/password/query"<br />
# {select password, salt from users where name='[ns_dbquoteval [lindex $args 0]]'}<br />
# config: "/security/salt/length" "64"<br />
# config: "/security/salt/dictionary" "0123456789abcdefghijkl..."<br />
</pre><br />
<br />
Basically the "expression" is used in a function, '''nsz_password''' to format a given clear-text password (varargs "args" to allow additional arguments to the function). The first argument is always the password.<br />
<br />
The "query" is executed as part of password-based authentication. The form handler reaches '''nsz_auth "myname" "mypassword"''' and the query is executed using the input list "myname". All row data beyond the first column, which must always be the password, is appended to the input password "mypassword" to produce the hash/salted/hash input "xpassword". This input "xpassword" is compared with the result of the returned value for the first column from the database query. If there is a match, password authentication succeeds for the user.<br />
<br />
Examples:<br />
<pre><br />
nsz_auth "sam" "correctpassword"<br />
# Query returns "sadf8vcx8vxasd7f7...","asduf7z6dfa..."<br />
# Expression eval for input passes "correctpassword","asduf7z6dfa..." and returns "sadf8vcx8vxasd7f7..."<br />
# Return value matches query<br />
# nsz_auth returns "sam"<br />
<br />
nsz_auth "sam" "badpassword"<br />
# Query returns "sadf8vcx8vxasd7f7...","asduf7z6dfa..."<br />
# Expression eval for input passes "badpassword","asduf7z6dfa..." and returns "yyzkfosd232cx7c..."<br />
# Return value does not match query<br />
# nsz_auth raises error "bad password"<br />
</pre><br />
<br />
Different configurations could use simple clear-text passwords, no salt, etc, simply by changing their configuration:<br />
<pre><br />
# config: "nsz/security/password/expression"<br />
# {lindex $args 0}<br />
# config: "nsz/security/password/query"<br />
# {select password from users where name='[ns_dbquoteval [lindex $args 0]]'}<br />
</pre><br />
<br />
The above would be the default configuration. For salt, the default would be size of 8 and dictionary of alphanumerics.<br />
<br />
Function '''nsz_salt''' can take 0, 1, or 2 arguments and returns the generated salt. The first argument is the length of the salt, defaults to config value. The second argument is the dictionary for the salt, default to config value.<br />
<br />
'''Question:''' How to make "users" table configurable? What about configuring which database pool to use? What about multiple authentication realms?<br />
<br />
----<br />
<br />
Sequences configuration should be as simple as specifying the database pool to use (default by default), the name of the sequence table, the size of the sequence chunk to claim when the local cache runs out of sequence numbers, and the number of retries before error during chunk claim. It could however be more complex, to specify the column names for the "name" and "value" of the sequence.<br />
<br />
Config:<br />
<pre><br />
# config: "nso/sequence/default/poolname" (default by default)<br />
# config: "nso/sequence/default/size" "100"<br />
# config: "nso/sequence/default/retry" "5"<br />
# config: "nso/sequence/default/table" "sequences_table"<br />
# config: "nso/sequence/default/name" "name_field"<br />
# config: "nso/sequence/default/value" "value_field"<br />
</pre><br />
<br />
Sequence defaults could be over-written per-sequence in similar fashion.<br />
<br />
Example usage:<br />
<pre><br />
set nextId [nso_sequence next "my_seq_name"]<br />
# returns 53 or error if fail<br />
</pre><br />
<br />
The function '''nso_sequence''' would thread-safe return the next sequence number it had available in its local nsv data, or if not available, claim the next chunk of 100 sequences numbers from the database:<br />
<pre><br />
# select value_field from sequences_table where name_field='my_seq_name'<br />
# result is 125, attempt to claim 100 values<br />
# update cave_sequences set value=225 where name_field='my_seq_name' and value_field=125<br />
</pre><br />
<br />
This would be retried up to ''5'' times.<br />
<br />
----<br />
<br />
Data layer notes:<br />
<br />
Config would map names like "users" to database pools and table names. Default would be default database pool and identity table name.<br />
<br />
Example usage:<br />
<pre><br />
# set nssValues [ns_set create]<br />
# ns_set update $nssValues "name" "sam"<br />
# ns_set update $nssValues "password" "mypassword"<br />
# ns_set put $nssValues "mail" "sam@caveman.org"<br />
# set nssUserKey [nso_row create "users" $nssValues]<br />
# set nssNewValues [ns_set create]<br />
# ns_set put $nssNewValues "mail" "samuelmb@gmail.com"<br />
# nso_row update "users" $nssUserKey $nssNewValues<br />
</pre><br />
<br />
Using ns_set instead of a model type-checking "nso_set" at least for now for simplicity and it would be the simple case.<br />
<br />
Additional config allows for data transforms:<br />
<pre><br />
# multi stage of filters and expressions:<br />
#<br />
# stage 0: accept-data-filter<br />
# e.g. "require a password is not null"<br />
# e.g. "require this integer be above zero"<br />
# e.g. "require id not be set"<br />
#<br />
# stage 1: transform-data-filter<br />
# config: expressions to apply to row:<br />
# e.g. "generate a salt"<br />
# ns_set update $nssData "salt" [nsz_salt]<br />
# e.g. "transform the password"<br />
# ns_set update $nssData "password" [nsz_password [ns_set get $nssData "password"] [ns_set get $nssData "salt"]]<br />
# e.g. "generate the next id from sequence"<br />
# ns_set update $nssData "id" [nso_sequence next "my_seq_name"]<br />
#<br />
# stage 2: veto-data-filter?<br />
#<br />
# allow multiple "inheritance" of data rules? or just defining rules that<br />
# can be referenced by multiple tables?<br />
</pre><br />
<br />
''very draft state''<br />
<br />
== useful links ==<br />
[http://philip.greenspun.com/doc/ philip.greenspun.com/doc/]<br />
[http://philip.greenspun.com/doc/data-pipeline data-pipeline]</div>Cavemanhttps://panoptic.com/mediawiki/aolserver/index.php?title=User_talk:Caveman&diff=4642User talk:Caveman2005-12-14T20:26:11Z<p>Caveman: /* cleaned up old conversations */</p>
<hr />
<div><br />
== towards a data and authentication layer ==<br />
<br />
It is possible that similar exists elsewhere (non-OpenACS) but I enjoy framework construction anyway. Services provided:<br />
# authentication (password check)<br />
# sequences<br />
# data layer<br />
<br />
----<br />
<br />
Authentication/Authorization config (nsz):<br />
<pre><br />
# config: "/security/password/expression"<br />
# {ns_sha1 [ns_md5 [lindex $args 0]] [lindex $args 1]}<br />
# config: "/security/password/query"<br />
# {select password, salt from users where name='[ns_dbquoteval [lindex $args 0]]'}<br />
# config: "/security/salt/length" "8"<br />
# config: "/security/salt/dictionary" "0123456789abcdefghijkl..."<br />
</pre><br />
<br />
Basically the "expression" is used in a function, '''nsz_password''' to format a given clear-text password (varargs "args" to allow additional arguments to the function). The first argument is always the password.<br />
<br />
The "query" is executed as part of password-based authentication. The form handler reaches '''nsz_auth "myname" "mypassword"''' and the query is executed using the input list "myname". All row data beyond the first column, which must always be the password, is appended to the input password "mypassword" to produce the hash/salted/hash input "xpassword". This input "xpassword" is compared with the result of the returned value for the first column from the database query. If there is a match, password authentication succeeds for the user.<br />
<br />
Examples:<br />
<pre><br />
nsz_auth "sam" "correctpassword"<br />
# Query returns "sadf8vcx8vxasd7f7...","asduf7z6dfa..."<br />
# Expression eval for input passes "correctpassword","asduf7z6dfa..." and returns "sadf8vcx8vxasd7f7..."<br />
# Return value matches query<br />
# nsz_auth returns "sam"<br />
<br />
nsz_auth "sam" "badpassword"<br />
# Query returns "sadf8vcx8vxasd7f7...","asduf7z6dfa..."<br />
# Expression eval for input passes "badpassword","asduf7z6dfa..." and returns "yyzkfosd232cx7c..."<br />
# Return value does not match query<br />
# nsz_auth raises error "bad password"<br />
</pre><br />
<br />
Different configurations could use simple clear-text passwords, no salt, etc, simply by changing their configuration:<br />
<pre><br />
# config: "nsz/security/password/expression"<br />
# {lindex $args 0}<br />
# config: "nsz/security/password/query"<br />
# {select password from users where name='[ns_dbquoteval [lindex $args 0]]'}<br />
</pre><br />
<br />
The above would be the default configuration. For salt, the default would be size of 8 and dictionary of alphanumerics.<br />
<br />
Function '''nsz_salt''' can take 0, 1, or 2 arguments and returns the generated salt. The first argument is the length of the salt, defaults to config value. The second argument is the dictionary for the salt, default to config value.<br />
<br />
'''Question:''' How to make "users" table configurable? What about configuring which database pool to use? What about multiple authentication realms?<br />
<br />
----<br />
<br />
Sequences configuration should be as simple as specifying the database pool to use (default by default), the name of the sequence table, the size of the sequence chunk to claim when the local cache runs out of sequence numbers, and the number of retries before error during chunk claim. It could however be more complex, to specify the column names for the "name" and "value" of the sequence.<br />
<br />
Config:<br />
<pre><br />
# config: "nso/sequence/default/poolname" (default by default)<br />
# config: "nso/sequence/default/size" "100"<br />
# config: "nso/sequence/default/retry" "5"<br />
# config: "nso/sequence/default/table" "sequences_table"<br />
# config: "nso/sequence/default/name" "name_field"<br />
# config: "nso/sequence/default/value" "value_field"<br />
</pre><br />
<br />
Sequence defaults could be over-written per-sequence in similar fashion.<br />
<br />
Example usage:<br />
<pre><br />
set nextId [nso_sequence next "my_seq_name"]<br />
# returns 53 or error if fail<br />
</pre><br />
<br />
The function '''nso_sequence''' would thread-safe return the next sequence number it had available in its local nsv data, or if not available, claim the next chunk of 100 sequences numbers from the database:<br />
<pre><br />
# select value_field from sequences_table where name_field='my_seq_name'<br />
# result is 125, attempt to claim 100 values<br />
# update cave_sequences set value=225 where name_field='my_seq_name' and value_field=125<br />
</pre><br />
<br />
This would be retried up to ''5'' times.<br />
<br />
----<br />
<br />
Data layer notes:<br />
<br />
Config would map names like "users" to database pools and table names. Default would be default database pool and identity table name.<br />
<br />
Example usage:<br />
<pre><br />
# set nssValues [ns_set create]<br />
# ns_set update $nssValues "name" "sam"<br />
# ns_set update $nssValues "password" "mypassword"<br />
# ns_set put $nssValues "mail" "sam@caveman.org"<br />
# set nssUserKey [nso_row create "users" $nssValues]<br />
# set nssNewValues [ns_set create]<br />
# ns_set put $nssNewValues "mail" "samuelmb@gmail.com"<br />
# nso_row update "users" $nssUserKey $nssNewValues<br />
</pre><br />
<br />
Using ns_set instead of a model type-checking "nso_set" at least for now for simplicity and it would be the simple case.<br />
<br />
Additional config allows for data transforms:<br />
<pre><br />
# multi stage of filters and expressions:<br />
#<br />
# stage 0: accept-data-filter<br />
# e.g. "require a password is not null"<br />
# e.g. "require this integer be above zero"<br />
# e.g. "require id not be set"<br />
#<br />
# stage 1: transform-data-filter<br />
# config: expressions to apply to row:<br />
# e.g. "generate a salt"<br />
# ns_set update $nssData "salt" [nsz_salt]<br />
# e.g. "transform the password"<br />
# ns_set update $nssData "password" [nsz_password [ns_set get $nssData "password"] [ns_set get $nssData "salt"]]<br />
# e.g. "generate the next id from sequence"<br />
# ns_set update $nssData "id" [nso_sequence next "my_seq_name"]<br />
#<br />
# stage 2: veto-data-filter?<br />
#<br />
# allow multiple "inheritance" of data rules? or just defining rules that<br />
# can be referenced by multiple tables?<br />
</pre><br />
<br />
''very draft state''<br />
<br />
== useful links ==<br />
[http://philip.greenspun.com/doc/ philip.greenspun.com/doc/]<br />
[http://philip.greenspun.com/doc/data-pipeline data-pipeline]</div>Cavemanhttps://panoptic.com/mediawiki/aolserver/index.php?title=User_talk:Caveman&diff=4641User talk:Caveman2005-12-14T20:20:52Z<p>Caveman: /* useful links */</p>
<hr />
<div>Hi, and welcome to the wiki! If you don't mind me asking, what's your full name (or do you want to remain anonymous)? Are you also subscribed to the [http://aolserver.com/lists.php AOLSERVER mailing list]? Some of us also hang out on [http://aolserver.com/chat/ IRC and chat] (you can also access the chat via AIM, but most folks use IRC).<br />
<br />
If you have any questions or concerns, don't hesitate to contact me. Thanks! ''-- [[User:Dossy|Dossy]] 07:13, 3 December 2005 (EST)''<br />
<br />
----<br />
<br />
Why does it seem like you're avoiding Tcl? Your recent wiki edits have been focused around other languages in AOLserver other than Tcl, like Lua, PHP and Ruby. Why? You will really never get the kind of performance out of Perl, PHP or Ruby as you will Tcl, because Tcl is suitable for embedding in a multi-threaded application where Perl, PHP and Ruby aren't. (I don't know enough about Lua to say one way or the other.) So, if you still want to use those other languages, then you probably don't care about performance at the high end, in which case, you probably don't need to use AOLserver, either. In the small, any web server will be more than adequate on modern hardware to serve a few hundred pages here and there. It's when you start getting into the few hundred per second arena where AOLserver has the opportunity to shine. ''-- [[User:Dossy|Dossy]] 07:46, 10 December 2005 (EST)''<br />
<br />
* Not at all -- I'm looking at other languages simply from the point of view of seeing how AOLServer modules are built at all. It has been a while since I did any heavy lifting with C, and I felt that tinkering with the module code would be a good refresher. Just scratching an itch. I use TCL heavily every day at work, and have no real knowledge of Lua either, it just seemed an opportune target to use when examining the general AOLServer module layer. --[[User:Caveman|Caveman]] 12:23, 12 December 2005 (EST) <br />
<br />
** Okay, cool. FYI, "AOLserver" is capitalized just like that, not "AOLServer" -- I'm picking nits, but the consistency is important to me. Thanks. :-) ''-- [[User:Dossy|Dossy]] 12:41, 12 December 2005 (EST)''<br />
<br />
*** Ack. I've been doing that on a ton of pages -- my mistake, I will try to use the correct capitalisation. --[[User:Caveman|Caveman]] 12:43, 12 December 2005 (EST)<br />
<br />
== towards a data and authentication layer ==<br />
<br />
It is possible that similar exists elsewhere (non-OpenACS) but I enjoy framework construction anyway. Services provided:<br />
# authentication (password check)<br />
# sequences<br />
# data layer<br />
<br />
----<br />
<br />
Authentication/Authorization config (nsz):<br />
<pre><br />
# config: "/security/password/expression"<br />
# {ns_sha1 [ns_md5 [lindex $args 0]] [lindex $args 1]}<br />
# config: "/security/password/query"<br />
# {select password, salt from users where name='[ns_dbquoteval [lindex $args 0]]'}<br />
# config: "/security/salt/length" "8"<br />
# config: "/security/salt/dictionary" "0123456789abcdefghijkl..."<br />
</pre><br />
<br />
Basically the "expression" is used in a function, '''nsz_password''' to format a given clear-text password (varargs "args" to allow additional arguments to the function). The first argument is always the password.<br />
<br />
The "query" is executed as part of password-based authentication. The form handler reaches '''nsz_auth "myname" "mypassword"''' and the query is executed using the input list "myname". All row data beyond the first column, which must always be the password, is appended to the input password "mypassword" to produce the hash/salted/hash input "xpassword". This input "xpassword" is compared with the result of the returned value for the first column from the database query. If there is a match, password authentication succeeds for the user.<br />
<br />
Examples:<br />
<pre><br />
nsz_auth "sam" "correctpassword"<br />
# Query returns "sadf8vcx8vxasd7f7...","asduf7z6dfa..."<br />
# Expression eval for input passes "correctpassword","asduf7z6dfa..." and returns "sadf8vcx8vxasd7f7..."<br />
# Return value matches query<br />
# nsz_auth returns "sam"<br />
<br />
nsz_auth "sam" "badpassword"<br />
# Query returns "sadf8vcx8vxasd7f7...","asduf7z6dfa..."<br />
# Expression eval for input passes "badpassword","asduf7z6dfa..." and returns "yyzkfosd232cx7c..."<br />
# Return value does not match query<br />
# nsz_auth raises error "bad password"<br />
</pre><br />
<br />
Different configurations could use simple clear-text passwords, no salt, etc, simply by changing their configuration:<br />
<pre><br />
# config: "nsz/security/password/expression"<br />
# {lindex $args 0}<br />
# config: "nsz/security/password/query"<br />
# {select password from users where name='[ns_dbquoteval [lindex $args 0]]'}<br />
</pre><br />
<br />
The above would be the default configuration. For salt, the default would be size of 8 and dictionary of alphanumerics.<br />
<br />
Function '''nsz_salt''' can take 0, 1, or 2 arguments and returns the generated salt. The first argument is the length of the salt, defaults to config value. The second argument is the dictionary for the salt, default to config value.<br />
<br />
'''Question:''' How to make "users" table configurable? What about configuring which database pool to use? What about multiple authentication realms?<br />
<br />
----<br />
<br />
Sequences configuration should be as simple as specifying the database pool to use (default by default), the name of the sequence table, the size of the sequence chunk to claim when the local cache runs out of sequence numbers, and the number of retries before error during chunk claim. It could however be more complex, to specify the column names for the "name" and "value" of the sequence.<br />
<br />
Config:<br />
<pre><br />
# config: "nso/sequence/default/poolname" (default by default)<br />
# config: "nso/sequence/default/size" "100"<br />
# config: "nso/sequence/default/retry" "5"<br />
# config: "nso/sequence/default/table" "sequences_table"<br />
# config: "nso/sequence/default/name" "name_field"<br />
# config: "nso/sequence/default/value" "value_field"<br />
</pre><br />
<br />
Sequence defaults could be over-written per-sequence in similar fashion.<br />
<br />
Example usage:<br />
<pre><br />
set nextId [nso_sequence next "my_seq_name"]<br />
# returns 53 or error if fail<br />
</pre><br />
<br />
The function '''nso_sequence''' would thread-safe return the next sequence number it had available in its local nsv data, or if not available, claim the next chunk of 100 sequences numbers from the database:<br />
<pre><br />
# select value_field from sequences_table where name_field='my_seq_name'<br />
# result is 125, attempt to claim 100 values<br />
# update cave_sequences set value=225 where name_field='my_seq_name' and value_field=125<br />
</pre><br />
<br />
This would be retried up to ''5'' times.<br />
<br />
----<br />
<br />
Data layer notes:<br />
<br />
Config would map names like "users" to database pools and table names. Default would be default database pool and identity table name.<br />
<br />
Example usage:<br />
<pre><br />
# set nssValues [ns_set create]<br />
# ns_set update $nssValues "name" "sam"<br />
# ns_set update $nssValues "password" "mypassword"<br />
# ns_set put $nssValues "mail" "sam@caveman.org"<br />
# set nssUserKey [nso_row create "users" $nssValues]<br />
# set nssNewValues [ns_set create]<br />
# ns_set put $nssNewValues "mail" "samuelmb@gmail.com"<br />
# nso_row update "users" $nssUserKey $nssNewValues<br />
</pre><br />
<br />
Using ns_set instead of a model type-checking "nso_set" at least for now for simplicity and it would be the simple case.<br />
<br />
Additional config allows for data transforms:<br />
<pre><br />
# multi stage of filters and expressions:<br />
#<br />
# stage 0: accept-data-filter<br />
# e.g. "require a password is not null"<br />
# e.g. "require this integer be above zero"<br />
# e.g. "require id not be set"<br />
#<br />
# stage 1: transform-data-filter<br />
# config: expressions to apply to row:<br />
# e.g. "generate a salt"<br />
# ns_set update $nssData "salt" [nsz_salt]<br />
# e.g. "transform the password"<br />
# ns_set update $nssData "password" [nsz_password [ns_set get $nssData "password"] [ns_set get $nssData "salt"]]<br />
# e.g. "generate the next id from sequence"<br />
# ns_set update $nssData "id" [nso_sequence next "my_seq_name"]<br />
#<br />
# stage 2: veto-data-filter?<br />
#<br />
# allow multiple "inheritance" of data rules? or just defining rules that<br />
# can be referenced by multiple tables?<br />
</pre><br />
<br />
''very draft state''<br />
<br />
== useful links ==<br />
[http://philip.greenspun.com/doc/ philip.greenspun.com/doc/]<br />
[http://philip.greenspun.com/doc/data-pipeline data-pipeline]</div>Cavemanhttps://panoptic.com/mediawiki/aolserver/index.php?title=User_talk:Caveman&diff=4640User talk:Caveman2005-12-14T20:20:28Z<p>Caveman: /* useful links */</p>
<hr />
<div>Hi, and welcome to the wiki! If you don't mind me asking, what's your full name (or do you want to remain anonymous)? Are you also subscribed to the [http://aolserver.com/lists.php AOLSERVER mailing list]? Some of us also hang out on [http://aolserver.com/chat/ IRC and chat] (you can also access the chat via AIM, but most folks use IRC).<br />
<br />
If you have any questions or concerns, don't hesitate to contact me. Thanks! ''-- [[User:Dossy|Dossy]] 07:13, 3 December 2005 (EST)''<br />
<br />
----<br />
<br />
Why does it seem like you're avoiding Tcl? Your recent wiki edits have been focused around other languages in AOLserver other than Tcl, like Lua, PHP and Ruby. Why? You will really never get the kind of performance out of Perl, PHP or Ruby as you will Tcl, because Tcl is suitable for embedding in a multi-threaded application where Perl, PHP and Ruby aren't. (I don't know enough about Lua to say one way or the other.) So, if you still want to use those other languages, then you probably don't care about performance at the high end, in which case, you probably don't need to use AOLserver, either. In the small, any web server will be more than adequate on modern hardware to serve a few hundred pages here and there. It's when you start getting into the few hundred per second arena where AOLserver has the opportunity to shine. ''-- [[User:Dossy|Dossy]] 07:46, 10 December 2005 (EST)''<br />
<br />
* Not at all -- I'm looking at other languages simply from the point of view of seeing how AOLServer modules are built at all. It has been a while since I did any heavy lifting with C, and I felt that tinkering with the module code would be a good refresher. Just scratching an itch. I use TCL heavily every day at work, and have no real knowledge of Lua either, it just seemed an opportune target to use when examining the general AOLServer module layer. --[[User:Caveman|Caveman]] 12:23, 12 December 2005 (EST) <br />
<br />
** Okay, cool. FYI, "AOLserver" is capitalized just like that, not "AOLServer" -- I'm picking nits, but the consistency is important to me. Thanks. :-) ''-- [[User:Dossy|Dossy]] 12:41, 12 December 2005 (EST)''<br />
<br />
*** Ack. I've been doing that on a ton of pages -- my mistake, I will try to use the correct capitalisation. --[[User:Caveman|Caveman]] 12:43, 12 December 2005 (EST)<br />
<br />
== towards a data and authentication layer ==<br />
<br />
It is possible that similar exists elsewhere (non-OpenACS) but I enjoy framework construction anyway. Services provided:<br />
# authentication (password check)<br />
# sequences<br />
# data layer<br />
<br />
----<br />
<br />
Authentication/Authorization config (nsz):<br />
<pre><br />
# config: "/security/password/expression"<br />
# {ns_sha1 [ns_md5 [lindex $args 0]] [lindex $args 1]}<br />
# config: "/security/password/query"<br />
# {select password, salt from users where name='[ns_dbquoteval [lindex $args 0]]'}<br />
# config: "/security/salt/length" "8"<br />
# config: "/security/salt/dictionary" "0123456789abcdefghijkl..."<br />
</pre><br />
<br />
Basically the "expression" is used in a function, '''nsz_password''' to format a given clear-text password (varargs "args" to allow additional arguments to the function). The first argument is always the password.<br />
<br />
The "query" is executed as part of password-based authentication. The form handler reaches '''nsz_auth "myname" "mypassword"''' and the query is executed using the input list "myname". All row data beyond the first column, which must always be the password, is appended to the input password "mypassword" to produce the hash/salted/hash input "xpassword". This input "xpassword" is compared with the result of the returned value for the first column from the database query. If there is a match, password authentication succeeds for the user.<br />
<br />
Examples:<br />
<pre><br />
nsz_auth "sam" "correctpassword"<br />
# Query returns "sadf8vcx8vxasd7f7...","asduf7z6dfa..."<br />
# Expression eval for input passes "correctpassword","asduf7z6dfa..." and returns "sadf8vcx8vxasd7f7..."<br />
# Return value matches query<br />
# nsz_auth returns "sam"<br />
<br />
nsz_auth "sam" "badpassword"<br />
# Query returns "sadf8vcx8vxasd7f7...","asduf7z6dfa..."<br />
# Expression eval for input passes "badpassword","asduf7z6dfa..." and returns "yyzkfosd232cx7c..."<br />
# Return value does not match query<br />
# nsz_auth raises error "bad password"<br />
</pre><br />
<br />
Different configurations could use simple clear-text passwords, no salt, etc, simply by changing their configuration:<br />
<pre><br />
# config: "nsz/security/password/expression"<br />
# {lindex $args 0}<br />
# config: "nsz/security/password/query"<br />
# {select password from users where name='[ns_dbquoteval [lindex $args 0]]'}<br />
</pre><br />
<br />
The above would be the default configuration. For salt, the default would be size of 8 and dictionary of alphanumerics.<br />
<br />
Function '''nsz_salt''' can take 0, 1, or 2 arguments and returns the generated salt. The first argument is the length of the salt, defaults to config value. The second argument is the dictionary for the salt, default to config value.<br />
<br />
'''Question:''' How to make "users" table configurable? What about configuring which database pool to use? What about multiple authentication realms?<br />
<br />
----<br />
<br />
Sequences configuration should be as simple as specifying the database pool to use (default by default), the name of the sequence table, the size of the sequence chunk to claim when the local cache runs out of sequence numbers, and the number of retries before error during chunk claim. It could however be more complex, to specify the column names for the "name" and "value" of the sequence.<br />
<br />
Config:<br />
<pre><br />
# config: "nso/sequence/default/poolname" (default by default)<br />
# config: "nso/sequence/default/size" "100"<br />
# config: "nso/sequence/default/retry" "5"<br />
# config: "nso/sequence/default/table" "sequences_table"<br />
# config: "nso/sequence/default/name" "name_field"<br />
# config: "nso/sequence/default/value" "value_field"<br />
</pre><br />
<br />
Sequence defaults could be over-written per-sequence in similar fashion.<br />
<br />
Example usage:<br />
<pre><br />
set nextId [nso_sequence next "my_seq_name"]<br />
# returns 53 or error if fail<br />
</pre><br />
<br />
The function '''nso_sequence''' would thread-safe return the next sequence number it had available in its local nsv data, or if not available, claim the next chunk of 100 sequences numbers from the database:<br />
<pre><br />
# select value_field from sequences_table where name_field='my_seq_name'<br />
# result is 125, attempt to claim 100 values<br />
# update cave_sequences set value=225 where name_field='my_seq_name' and value_field=125<br />
</pre><br />
<br />
This would be retried up to ''5'' times.<br />
<br />
----<br />
<br />
Data layer notes:<br />
<br />
Config would map names like "users" to database pools and table names. Default would be default database pool and identity table name.<br />
<br />
Example usage:<br />
<pre><br />
# set nssValues [ns_set create]<br />
# ns_set update $nssValues "name" "sam"<br />
# ns_set update $nssValues "password" "mypassword"<br />
# ns_set put $nssValues "mail" "sam@caveman.org"<br />
# set nssUserKey [nso_row create "users" $nssValues]<br />
# set nssNewValues [ns_set create]<br />
# ns_set put $nssNewValues "mail" "samuelmb@gmail.com"<br />
# nso_row update "users" $nssUserKey $nssNewValues<br />
</pre><br />
<br />
Using ns_set instead of a model type-checking "nso_set" at least for now for simplicity and it would be the simple case.<br />
<br />
Additional config allows for data transforms:<br />
<pre><br />
# multi stage of filters and expressions:<br />
#<br />
# stage 0: accept-data-filter<br />
# e.g. "require a password is not null"<br />
# e.g. "require this integer be above zero"<br />
# e.g. "require id not be set"<br />
#<br />
# stage 1: transform-data-filter<br />
# config: expressions to apply to row:<br />
# e.g. "generate a salt"<br />
# ns_set update $nssData "salt" [nsz_salt]<br />
# e.g. "transform the password"<br />
# ns_set update $nssData "password" [nsz_password [ns_set get $nssData "password"] [ns_set get $nssData "salt"]]<br />
# e.g. "generate the next id from sequence"<br />
# ns_set update $nssData "id" [nso_sequence next "my_seq_name"]<br />
#<br />
# stage 2: veto-data-filter?<br />
#<br />
# allow multiple "inheritance" of data rules? or just defining rules that<br />
# can be referenced by multiple tables?<br />
</pre><br />
<br />
''very draft state''<br />
<br />
== useful links ==<br />
[http://philip.greenspun.com/doc/ philip.greenspun.com/doc/]<br />
[http://philip.greenspun.com/doc/data-pipeline philip.greenspun.com/doc/data-pipeline]</div>Cavemanhttps://panoptic.com/mediawiki/aolserver/index.php?title=User_talk:Caveman&diff=4639User talk:Caveman2005-12-14T20:19:51Z<p>Caveman: useful links</p>
<hr />
<div>Hi, and welcome to the wiki! If you don't mind me asking, what's your full name (or do you want to remain anonymous)? Are you also subscribed to the [http://aolserver.com/lists.php AOLSERVER mailing list]? Some of us also hang out on [http://aolserver.com/chat/ IRC and chat] (you can also access the chat via AIM, but most folks use IRC).<br />
<br />
If you have any questions or concerns, don't hesitate to contact me. Thanks! ''-- [[User:Dossy|Dossy]] 07:13, 3 December 2005 (EST)''<br />
<br />
----<br />
<br />
Why does it seem like you're avoiding Tcl? Your recent wiki edits have been focused around other languages in AOLserver other than Tcl, like Lua, PHP and Ruby. Why? You will really never get the kind of performance out of Perl, PHP or Ruby as you will Tcl, because Tcl is suitable for embedding in a multi-threaded application where Perl, PHP and Ruby aren't. (I don't know enough about Lua to say one way or the other.) So, if you still want to use those other languages, then you probably don't care about performance at the high end, in which case, you probably don't need to use AOLserver, either. In the small, any web server will be more than adequate on modern hardware to serve a few hundred pages here and there. It's when you start getting into the few hundred per second arena where AOLserver has the opportunity to shine. ''-- [[User:Dossy|Dossy]] 07:46, 10 December 2005 (EST)''<br />
<br />
* Not at all -- I'm looking at other languages simply from the point of view of seeing how AOLServer modules are built at all. It has been a while since I did any heavy lifting with C, and I felt that tinkering with the module code would be a good refresher. Just scratching an itch. I use TCL heavily every day at work, and have no real knowledge of Lua either, it just seemed an opportune target to use when examining the general AOLServer module layer. --[[User:Caveman|Caveman]] 12:23, 12 December 2005 (EST) <br />
<br />
** Okay, cool. FYI, "AOLserver" is capitalized just like that, not "AOLServer" -- I'm picking nits, but the consistency is important to me. Thanks. :-) ''-- [[User:Dossy|Dossy]] 12:41, 12 December 2005 (EST)''<br />
<br />
*** Ack. I've been doing that on a ton of pages -- my mistake, I will try to use the correct capitalisation. --[[User:Caveman|Caveman]] 12:43, 12 December 2005 (EST)<br />
<br />
== towards a data and authentication layer ==<br />
<br />
It is possible that similar exists elsewhere (non-OpenACS) but I enjoy framework construction anyway. Services provided:<br />
# authentication (password check)<br />
# sequences<br />
# data layer<br />
<br />
----<br />
<br />
Authentication/Authorization config (nsz):<br />
<pre><br />
# config: "/security/password/expression"<br />
# {ns_sha1 [ns_md5 [lindex $args 0]] [lindex $args 1]}<br />
# config: "/security/password/query"<br />
# {select password, salt from users where name='[ns_dbquoteval [lindex $args 0]]'}<br />
# config: "/security/salt/length" "8"<br />
# config: "/security/salt/dictionary" "0123456789abcdefghijkl..."<br />
</pre><br />
<br />
Basically the "expression" is used in a function, '''nsz_password''' to format a given clear-text password (varargs "args" to allow additional arguments to the function). The first argument is always the password.<br />
<br />
The "query" is executed as part of password-based authentication. The form handler reaches '''nsz_auth "myname" "mypassword"''' and the query is executed using the input list "myname". All row data beyond the first column, which must always be the password, is appended to the input password "mypassword" to produce the hash/salted/hash input "xpassword". This input "xpassword" is compared with the result of the returned value for the first column from the database query. If there is a match, password authentication succeeds for the user.<br />
<br />
Examples:<br />
<pre><br />
nsz_auth "sam" "correctpassword"<br />
# Query returns "sadf8vcx8vxasd7f7...","asduf7z6dfa..."<br />
# Expression eval for input passes "correctpassword","asduf7z6dfa..." and returns "sadf8vcx8vxasd7f7..."<br />
# Return value matches query<br />
# nsz_auth returns "sam"<br />
<br />
nsz_auth "sam" "badpassword"<br />
# Query returns "sadf8vcx8vxasd7f7...","asduf7z6dfa..."<br />
# Expression eval for input passes "badpassword","asduf7z6dfa..." and returns "yyzkfosd232cx7c..."<br />
# Return value does not match query<br />
# nsz_auth raises error "bad password"<br />
</pre><br />
<br />
Different configurations could use simple clear-text passwords, no salt, etc, simply by changing their configuration:<br />
<pre><br />
# config: "nsz/security/password/expression"<br />
# {lindex $args 0}<br />
# config: "nsz/security/password/query"<br />
# {select password from users where name='[ns_dbquoteval [lindex $args 0]]'}<br />
</pre><br />
<br />
The above would be the default configuration. For salt, the default would be size of 8 and dictionary of alphanumerics.<br />
<br />
Function '''nsz_salt''' can take 0, 1, or 2 arguments and returns the generated salt. The first argument is the length of the salt, defaults to config value. The second argument is the dictionary for the salt, default to config value.<br />
<br />
'''Question:''' How to make "users" table configurable? What about configuring which database pool to use? What about multiple authentication realms?<br />
<br />
----<br />
<br />
Sequences configuration should be as simple as specifying the database pool to use (default by default), the name of the sequence table, the size of the sequence chunk to claim when the local cache runs out of sequence numbers, and the number of retries before error during chunk claim. It could however be more complex, to specify the column names for the "name" and "value" of the sequence.<br />
<br />
Config:<br />
<pre><br />
# config: "nso/sequence/default/poolname" (default by default)<br />
# config: "nso/sequence/default/size" "100"<br />
# config: "nso/sequence/default/retry" "5"<br />
# config: "nso/sequence/default/table" "sequences_table"<br />
# config: "nso/sequence/default/name" "name_field"<br />
# config: "nso/sequence/default/value" "value_field"<br />
</pre><br />
<br />
Sequence defaults could be over-written per-sequence in similar fashion.<br />
<br />
Example usage:<br />
<pre><br />
set nextId [nso_sequence next "my_seq_name"]<br />
# returns 53 or error if fail<br />
</pre><br />
<br />
The function '''nso_sequence''' would thread-safe return the next sequence number it had available in its local nsv data, or if not available, claim the next chunk of 100 sequences numbers from the database:<br />
<pre><br />
# select value_field from sequences_table where name_field='my_seq_name'<br />
# result is 125, attempt to claim 100 values<br />
# update cave_sequences set value=225 where name_field='my_seq_name' and value_field=125<br />
</pre><br />
<br />
This would be retried up to ''5'' times.<br />
<br />
----<br />
<br />
Data layer notes:<br />
<br />
Config would map names like "users" to database pools and table names. Default would be default database pool and identity table name.<br />
<br />
Example usage:<br />
<pre><br />
# set nssValues [ns_set create]<br />
# ns_set update $nssValues "name" "sam"<br />
# ns_set update $nssValues "password" "mypassword"<br />
# ns_set put $nssValues "mail" "sam@caveman.org"<br />
# set nssUserKey [nso_row create "users" $nssValues]<br />
# set nssNewValues [ns_set create]<br />
# ns_set put $nssNewValues "mail" "samuelmb@gmail.com"<br />
# nso_row update "users" $nssUserKey $nssNewValues<br />
</pre><br />
<br />
Using ns_set instead of a model type-checking "nso_set" at least for now for simplicity and it would be the simple case.<br />
<br />
Additional config allows for data transforms:<br />
<pre><br />
# multi stage of filters and expressions:<br />
#<br />
# stage 0: accept-data-filter<br />
# e.g. "require a password is not null"<br />
# e.g. "require this integer be above zero"<br />
# e.g. "require id not be set"<br />
#<br />
# stage 1: transform-data-filter<br />
# config: expressions to apply to row:<br />
# e.g. "generate a salt"<br />
# ns_set update $nssData "salt" [nsz_salt]<br />
# e.g. "transform the password"<br />
# ns_set update $nssData "password" [nsz_password [ns_set get $nssData "password"] [ns_set get $nssData "salt"]]<br />
# e.g. "generate the next id from sequence"<br />
# ns_set update $nssData "id" [nso_sequence next "my_seq_name"]<br />
#<br />
# stage 2: veto-data-filter?<br />
#<br />
# allow multiple "inheritance" of data rules? or just defining rules that<br />
# can be referenced by multiple tables?<br />
</pre><br />
<br />
''very draft state''<br />
<br />
== useful links ==<br />
<br />
[http://philip.greenspun.com/doc/data-pipeline]</div>Cavemanhttps://panoptic.com/mediawiki/aolserver/index.php?title=User:Caveman&diff=4638User:Caveman2005-12-14T20:15:58Z<p>Caveman: </p>
<hr />
<div>[mailto:sam@caveman.org Samuel Montgomery-Blinn]<br />
<br />
An off-and-on hobbyist user of Aolserver from 3.x days. Never been an OpenACS fan, hope that doesn't get me into trouble someday. My Aolserver runs on Debian 3.1 using the aolserver4-* binary packages, so I thank the maintainers for their time and effort.<br />
<br />
'''Current interests:'''<br />
<br />
Best Practices on cookie management and session management with AOLServer<br />
<br />
Best Pratcices for identity management and authorization model AOLServer<br />
<br />
Tinkering with a standardised phpinfo() alike command: [http://caveman.org/info/]<br />
<br />
Blogging/discussion software, especially usefully multi-user.<br />
<br />
SVG graphics generation.<br />
<br />
Application model and management.<br />
<br />
nsdbeans data layer (similar to Java's EJB, or Python's SQLObject).<br />
<br />
SOAP conversation with directi's reseller server [http://manage.directi.com/kb/servlet/KBServlet/cat106.html]<br />
<br />
...<br />
<br />
'''Current 'real' work:'''<br />
<br />
A lot of JACL/TCL scripting in the test automation world for "nameless big software company". WebSphere includes a JACL administrative shell that is quite useful for scripting all kinds of configuration and test activity for J2EE applications.</div>Cavemanhttps://panoptic.com/mediawiki/aolserver/index.php?title=User_talk:Caveman&diff=4637User talk:Caveman2005-12-14T20:15:36Z<p>Caveman: </p>
<hr />
<div>Hi, and welcome to the wiki! If you don't mind me asking, what's your full name (or do you want to remain anonymous)? Are you also subscribed to the [http://aolserver.com/lists.php AOLSERVER mailing list]? Some of us also hang out on [http://aolserver.com/chat/ IRC and chat] (you can also access the chat via AIM, but most folks use IRC).<br />
<br />
If you have any questions or concerns, don't hesitate to contact me. Thanks! ''-- [[User:Dossy|Dossy]] 07:13, 3 December 2005 (EST)''<br />
<br />
----<br />
<br />
Why does it seem like you're avoiding Tcl? Your recent wiki edits have been focused around other languages in AOLserver other than Tcl, like Lua, PHP and Ruby. Why? You will really never get the kind of performance out of Perl, PHP or Ruby as you will Tcl, because Tcl is suitable for embedding in a multi-threaded application where Perl, PHP and Ruby aren't. (I don't know enough about Lua to say one way or the other.) So, if you still want to use those other languages, then you probably don't care about performance at the high end, in which case, you probably don't need to use AOLserver, either. In the small, any web server will be more than adequate on modern hardware to serve a few hundred pages here and there. It's when you start getting into the few hundred per second arena where AOLserver has the opportunity to shine. ''-- [[User:Dossy|Dossy]] 07:46, 10 December 2005 (EST)''<br />
<br />
* Not at all -- I'm looking at other languages simply from the point of view of seeing how AOLServer modules are built at all. It has been a while since I did any heavy lifting with C, and I felt that tinkering with the module code would be a good refresher. Just scratching an itch. I use TCL heavily every day at work, and have no real knowledge of Lua either, it just seemed an opportune target to use when examining the general AOLServer module layer. --[[User:Caveman|Caveman]] 12:23, 12 December 2005 (EST) <br />
<br />
** Okay, cool. FYI, "AOLserver" is capitalized just like that, not "AOLServer" -- I'm picking nits, but the consistency is important to me. Thanks. :-) ''-- [[User:Dossy|Dossy]] 12:41, 12 December 2005 (EST)''<br />
<br />
*** Ack. I've been doing that on a ton of pages -- my mistake, I will try to use the correct capitalisation. --[[User:Caveman|Caveman]] 12:43, 12 December 2005 (EST)<br />
<br />
== towards a data and authentication layer ==<br />
<br />
It is possible that similar exists elsewhere (non-OpenACS) but I enjoy framework construction anyway. Services provided:<br />
# authentication (password check)<br />
# sequences<br />
# data layer<br />
<br />
----<br />
<br />
Authentication/Authorization config (nsz):<br />
<pre><br />
# config: "/security/password/expression"<br />
# {ns_sha1 [ns_md5 [lindex $args 0]] [lindex $args 1]}<br />
# config: "/security/password/query"<br />
# {select password, salt from users where name='[ns_dbquoteval [lindex $args 0]]'}<br />
# config: "/security/salt/length" "8"<br />
# config: "/security/salt/dictionary" "0123456789abcdefghijkl..."<br />
</pre><br />
<br />
Basically the "expression" is used in a function, '''nsz_password''' to format a given clear-text password (varargs "args" to allow additional arguments to the function). The first argument is always the password.<br />
<br />
The "query" is executed as part of password-based authentication. The form handler reaches '''nsz_auth "myname" "mypassword"''' and the query is executed using the input list "myname". All row data beyond the first column, which must always be the password, is appended to the input password "mypassword" to produce the hash/salted/hash input "xpassword". This input "xpassword" is compared with the result of the returned value for the first column from the database query. If there is a match, password authentication succeeds for the user.<br />
<br />
Examples:<br />
<pre><br />
nsz_auth "sam" "correctpassword"<br />
# Query returns "sadf8vcx8vxasd7f7...","asduf7z6dfa..."<br />
# Expression eval for input passes "correctpassword","asduf7z6dfa..." and returns "sadf8vcx8vxasd7f7..."<br />
# Return value matches query<br />
# nsz_auth returns "sam"<br />
<br />
nsz_auth "sam" "badpassword"<br />
# Query returns "sadf8vcx8vxasd7f7...","asduf7z6dfa..."<br />
# Expression eval for input passes "badpassword","asduf7z6dfa..." and returns "yyzkfosd232cx7c..."<br />
# Return value does not match query<br />
# nsz_auth raises error "bad password"<br />
</pre><br />
<br />
Different configurations could use simple clear-text passwords, no salt, etc, simply by changing their configuration:<br />
<pre><br />
# config: "nsz/security/password/expression"<br />
# {lindex $args 0}<br />
# config: "nsz/security/password/query"<br />
# {select password from users where name='[ns_dbquoteval [lindex $args 0]]'}<br />
</pre><br />
<br />
The above would be the default configuration. For salt, the default would be size of 8 and dictionary of alphanumerics.<br />
<br />
Function '''nsz_salt''' can take 0, 1, or 2 arguments and returns the generated salt. The first argument is the length of the salt, defaults to config value. The second argument is the dictionary for the salt, default to config value.<br />
<br />
'''Question:''' How to make "users" table configurable? What about configuring which database pool to use? What about multiple authentication realms?<br />
<br />
----<br />
<br />
Sequences configuration should be as simple as specifying the database pool to use (default by default), the name of the sequence table, the size of the sequence chunk to claim when the local cache runs out of sequence numbers, and the number of retries before error during chunk claim. It could however be more complex, to specify the column names for the "name" and "value" of the sequence.<br />
<br />
Config:<br />
<pre><br />
# config: "nso/sequence/default/poolname" (default by default)<br />
# config: "nso/sequence/default/size" "100"<br />
# config: "nso/sequence/default/retry" "5"<br />
# config: "nso/sequence/default/table" "sequences_table"<br />
# config: "nso/sequence/default/name" "name_field"<br />
# config: "nso/sequence/default/value" "value_field"<br />
</pre><br />
<br />
Sequence defaults could be over-written per-sequence in similar fashion.<br />
<br />
Example usage:<br />
<pre><br />
set nextId [nso_sequence next "my_seq_name"]<br />
# returns 53 or error if fail<br />
</pre><br />
<br />
The function '''nso_sequence''' would thread-safe return the next sequence number it had available in its local nsv data, or if not available, claim the next chunk of 100 sequences numbers from the database:<br />
<pre><br />
# select value_field from sequences_table where name_field='my_seq_name'<br />
# result is 125, attempt to claim 100 values<br />
# update cave_sequences set value=225 where name_field='my_seq_name' and value_field=125<br />
</pre><br />
<br />
This would be retried up to ''5'' times.<br />
<br />
----<br />
<br />
Data layer notes:<br />
<br />
Config would map names like "users" to database pools and table names. Default would be default database pool and identity table name.<br />
<br />
Example usage:<br />
<pre><br />
# set nssValues [ns_set create]<br />
# ns_set update $nssValues "name" "sam"<br />
# ns_set update $nssValues "password" "mypassword"<br />
# ns_set put $nssValues "mail" "sam@caveman.org"<br />
# set nssUserKey [nso_row create "users" $nssValues]<br />
# set nssNewValues [ns_set create]<br />
# ns_set put $nssNewValues "mail" "samuelmb@gmail.com"<br />
# nso_row update "users" $nssUserKey $nssNewValues<br />
</pre><br />
<br />
Using ns_set instead of a model type-checking "nso_set" at least for now for simplicity and it would be the simple case.<br />
<br />
Additional config allows for data transforms:<br />
<pre><br />
# multi stage of filters and expressions:<br />
#<br />
# stage 0: accept-data-filter<br />
# e.g. "require a password is not null"<br />
# e.g. "require this integer be above zero"<br />
# e.g. "require id not be set"<br />
#<br />
# stage 1: transform-data-filter<br />
# config: expressions to apply to row:<br />
# e.g. "generate a salt"<br />
# ns_set update $nssData "salt" [nsz_salt]<br />
# e.g. "transform the password"<br />
# ns_set update $nssData "password" [nsz_password [ns_set get $nssData "password"] [ns_set get $nssData "salt"]]<br />
# e.g. "generate the next id from sequence"<br />
# ns_set update $nssData "id" [nso_sequence next "my_seq_name"]<br />
#<br />
# stage 2: veto-data-filter?<br />
#<br />
# allow multiple "inheritance" of data rules? or just defining rules that<br />
# can be referenced by multiple tables?<br />
</pre><br />
<br />
''very draft state''</div>Cavemanhttps://panoptic.com/mediawiki/aolserver/index.php?title=Frequently_Asked_Questions&diff=4636Frequently Asked Questions2005-12-14T19:45:20Z<p>Caveman: /* changed should no longer be necessary to stronger language for package require example */</p>
<hr />
<div>'''Frequently Asked Questions'''<br />
<br />
(Please add new questions at the very bottom of the list. Thanks.)<br />
<br />
----<br />
<br />
'''What is AOLserver?'''<br />
<br />
AOLserver is America Online's Open Source web server. AOLserver is the backbone of the largest and busiest production environments in the world.<br />
<br />
AOLserver is a multithreaded, Tcl-enabled, massively-scalable and extensible web server tuned for large scale, dynamic web sites. AOLserver also includes complete database integration and a dynamic page scripting language.<br />
<br />
----<br />
<br />
'''What is the latest version of AOLserver?'''<br />
* The latest stable 3.4.x version is 3.4.2 released 18 September 2001.<br />
* The latest stable 3.5.x version is 3.5.11 released 17 October 2003.<br />
* The latest stable 4.0.x version is 4.0.10 released 18 January 2005.<br />
* Current development (CVS HEAD) is 4.1.0a.<br />
<br />
----<br />
<br />
'''Where can I get AOLserver?'''<br />
<br />
The AOLserver project is hosted at [http://sourceforge.net/ SourceForge], and file releases are available for [[download]] in the [http://sourceforge.net/project/showfiles.php?group_id=3152 AOLserver Project Filelist].<br />
<br />
----<br />
<br />
'''What platforms does AOLserver support?'''<br />
<br />
'''AOLserver''' is known to compile and run on the following platforms:<br />
* Linux 2.2 (i386), 2.4 and 2.6<br />
* Windows 95/98/NT/2K/XP (i386) (partially supported, see #6)<br />
* FreeBSD 3.4 (i386)<br />
* OpenBSD 2.5 (i386)<br />
* UnixWare 7.x (i386)<br />
* DEC Tru64 & OSF/1 4.0 (alpha)<br />
* Solaris 2.x (sparc), Solaris 2.10 (x86)<br />
* HP/UX 10 & 11 (hppa)<br />
* Irix 6.x (mips)<br />
* Apple MacOS X 10.3 (ppc), 10.4 (ppc)<br />
<br />
----<br />
<br />
'''How is AOLserver licensed and distributed?'''<br />
<br />
Via the [[AOLserver Public License]], viewable at http://aolserver.com/license/.<br />
<br />
----<br />
<br />
'''How does AOLserver performance compare to other major servers?'''<br />
<br />
[[Brady Wetherington]] says: On Unix, AOLserver can generate many, many dynamic pages very quickly and reliably. It also has some special code paths designed to speed up processing of static pages (fastpath), though I don't use that very much, personally. Along with the database connection pools, it's definitely one of the highest-performance web-based database systems I've used.<br />
<br />
<br />
'''How is it different from Apache HTTP Server?'''<br />
<br />
The current Apache HTTP Server<br />
* is part of / a project of the Apache Software Foundation. The process of development and decision making is working for years and accepted by all participants<br />
* allows to run applications in a process-pre-forking or multi-threaded environment by design<br />
* is the leading webserver, so it is widely known, accepted and supported<br />
* is itself a subproject accompanied by lots of well known other projects and frameworks (like Ant, Jakarta, Struts...)<br />
<br />
In contrast AOLserver<br />
* can do lots of use cases that are done with Apache modules with a few lines of TCL code (via registered filters and procs)<br />
* is bound to its multi-threaded architecture that has its own disadvantages, depending on what you want to do<br />
<br />
'''How is it different from <insert other webserver>?'''<br />
<br />
???<br />
<br />
----<br />
<br />
'''Where is AOLserver appropriate? Where is it not?'''<br />
<br />
It is not appropriate...<br />
* when you want to do virtual hosting for multiple customers. For static content, AOLserver is fine - you're just serving static content. For dynamic, server-side functionality, to get the level of privilege separation necessary, you'd have to run a separate nsd per customer to ensure that one customer can't access the content/data of another's. There are apparently some folks out there who have set up AOLserver just this way and are doing just this.<br />
* when the code you want to use is not thread-safe (and you are not able to change that)<br />
* when your main application makes heavy use of cgi-tools or other scripting languages like PHP or Phython (in general: where currently no active dedicated maintainer for corresponding modules is known)<br />
* when you need backup of a large world wide community that uses tools, modules and code you can find and read in every single computer magazine. AOLserver and TCL are niche products, which only means they are not sexy to the broad audience, but are used intensively by a sophisticated, intelligent minority<br />
* when you know you would need more than one day to convince your customer to use it (in other words: if you use technology the first time don't let your most important customer be the beta tester)<br />
<br />
It is appropriate...<br />
* when you want to make maximum use of your machines hardware ressources: AOLserver is a highly configurable beast that allows you to run big websites<br />
* when you plan to run a website that makes heavy use of one or more databases (using pooled connections)<br />
* when you want to cache lots or all of your static files (.html,.gif,.css.,.js ...) in your servers memory (via modules fastpath and nscache)<br />
* when you like the good feeling of running and coding your apps on a well-tested multi-threaded server architecture. The server never has been a process-forking one.<br />
<br />
<br />
The idea here is if you know your requirements and your scope is fairly stable and you feel comfortable you can predict the future, and if all signs point to the app. remaining small-to-medium in usage/traffic, then pick whatever platform or technology you like the best -- it really won't make a difference. But, if you think that it's a very real possibility you'll need<br />
to scale up capacity to meet growing demand/traffic, possibly indefinitely, then yes, the hidden cost of re-architecting or migrating to a different technology can be a killer when you have to use the words "sunk cost" to describe the originally developed system. In that case, you may be better off starting with implementing with AOLserver, as its performance "ceiling" so to speak is higher than other technologies. (TODO: Benchmarks demonstrating this empirically?)<br />
<br />
----<br />
<br />
'''How do I get started with AOLserver?'''<br />
<br />
<need to link to a newbie guide HOWTO><br />
<br />
----<br />
<br />
'''How can I learn more about AOLserver?'''<br />
<br />
Start by reading the [[Documentation]], which is still a work-in-progress.<br />
<br />
----<br />
<br />
'''"package require" doesn't work! What's wrong?'''<br />
<br />
Here's the relevant portion of a message [[Dossy Shiobara]] sent to the AOLserver mailing list back on 16 June 2000:<br />
<br />
set tcl_library [file join $tcl_pkgPath tcl${tcl_version}]<br />
source [file join $tcl_library init.tcl]<br />
<br />
package require works like a charm after that :-)<br />
<br />
There you have it. Perhaps, some day, this won't be a necessary step. But, in the meantime ...<br />
<br />
''As of AOLserver 4.0 and perhaps even a late version of 3.5.x, this step is no longer necessary.''<br />
<br />
----<br />
<br />
'''"ns_set update [ns_conn outputheaders $conn] Content-Type {application/x-tcl}" does not work in .adp files as I wish. The server always returns two copies of the Content-Type header, one as application/x-tcl, another as text/html and clients(galeon, tcl http package) always use the second. How do I remove the second Content-Type?'''<br />
<br />
Good question -- this is really a bug that needs to be fixed in the server code itself.<br />
<br />
----<br />
<br />
'''How can I get Tclet scripts served from AOLserver to run inside the Tcl Plugin?'''<br />
<br />
Someone asks: ''I have an aolserver for OpenACS. I installed Tcl Plugin which works well with classic Tclets on Tcl Plugin Home Pages. But with Aolserver, it doesn't work.... Do you know the answer of this?''<br />
<br />
----<br />
<br />
'''How can I compile AOLserver on HP-UX, both 10.20 and 11.x?'''<br />
<br />
[[Dossy]]: Good question. If I had easy access to HP-UX machines, I'd try it myself. AOLserver 4.x should hopefully build on HP-UX without any changes, but I'm only guessing.<br />
<br />
HPUX doesn't implement a lot of BSD/POSIX IPC functions, or so I hear.<br />
<br />
----<br />
<br />
'''I'm getting an error compiling AOLserver about POLLIN, POLLOUT and POLLPRI being redefined. What's wrong?'''<br />
<br />
AOLserver requires that the "configure" script be run using the GNU C (gcc) compiler. Try running the configure script like this:<br />
<br />
$ CC=gcc ./configure --args...<br />
<br />
----<br />
<br />
'''Does AOLserver support HTTP Keep-Alive? I'm sending a HTTP/1.1 request via httperf and AOLserver isn't doing Keep-Alive like Apache does! What's wrong?'''<br />
<br />
Actually, nothing is wrong. You just need to tell httperf to include the headers that tell AOLserver to expect multiple requests per connection. Add '--add_header "Connection: Keep-Alive\n"' to your httperf request. <br />
<br />
The issue is that Apache and AOLserver chose opposite default behaviors when interpretting [http://www.ietf.org/rfc/rfc2068.txt RFC 2068 section 8.1.2.1]:<br />
<br />
An HTTP/1.1 server MAY assume that a HTTP/1.1 client intends to<br />
maintain a persistent connection unless a Connection header including<br />
the connection-token "close" was sent in the request. If the server<br />
chooses to close the connection immediately after sending the<br />
response, it SHOULD send a Connection header including the<br />
connection-token close.<br />
<br />
An HTTP/1.1 client MAY expect a connection to remain open, but would<br />
decide to keep it open based on whether the response from a server<br />
contains a Connection header with the connection-token close. In case<br />
the client does not want to maintain a connection for more than that<br />
request, it SHOULD send a Connection header including the<br />
connection-token close.<br />
<br />
The key here is "MAY" -- AOLserver (currently, as of 4.0.10) chooses not to assume a Keep-Alive connection unless the client explicitly requests it by sending "Connection: Keep-Alive" in the HTTP request header. This may change in the future (HTTP/1.1 requests default to Keep-Alive unless the client explicitly sends "Connection: close" -- apparently this is how Apache works).<br />
<br />
----<br />
<br />
[[Category Documentation]]</div>Cavemanhttps://panoptic.com/mediawiki/aolserver/index.php?title=Frequently_Asked_Questions&diff=4635Frequently Asked Questions2005-12-14T19:43:43Z<p>Caveman: /* fixed brackets in code sample for package require */</p>
<hr />
<div>'''Frequently Asked Questions'''<br />
<br />
(Please add new questions at the very bottom of the list. Thanks.)<br />
<br />
----<br />
<br />
'''What is AOLserver?'''<br />
<br />
AOLserver is America Online's Open Source web server. AOLserver is the backbone of the largest and busiest production environments in the world.<br />
<br />
AOLserver is a multithreaded, Tcl-enabled, massively-scalable and extensible web server tuned for large scale, dynamic web sites. AOLserver also includes complete database integration and a dynamic page scripting language.<br />
<br />
----<br />
<br />
'''What is the latest version of AOLserver?'''<br />
* The latest stable 3.4.x version is 3.4.2 released 18 September 2001.<br />
* The latest stable 3.5.x version is 3.5.11 released 17 October 2003.<br />
* The latest stable 4.0.x version is 4.0.10 released 18 January 2005.<br />
* Current development (CVS HEAD) is 4.1.0a.<br />
<br />
----<br />
<br />
'''Where can I get AOLserver?'''<br />
<br />
The AOLserver project is hosted at [http://sourceforge.net/ SourceForge], and file releases are available for [[download]] in the [http://sourceforge.net/project/showfiles.php?group_id=3152 AOLserver Project Filelist].<br />
<br />
----<br />
<br />
'''What platforms does AOLserver support?'''<br />
<br />
'''AOLserver''' is known to compile and run on the following platforms:<br />
* Linux 2.2 (i386), 2.4 and 2.6<br />
* Windows 95/98/NT/2K/XP (i386) (partially supported, see #6)<br />
* FreeBSD 3.4 (i386)<br />
* OpenBSD 2.5 (i386)<br />
* UnixWare 7.x (i386)<br />
* DEC Tru64 & OSF/1 4.0 (alpha)<br />
* Solaris 2.x (sparc), Solaris 2.10 (x86)<br />
* HP/UX 10 & 11 (hppa)<br />
* Irix 6.x (mips)<br />
* Apple MacOS X 10.3 (ppc), 10.4 (ppc)<br />
<br />
----<br />
<br />
'''How is AOLserver licensed and distributed?'''<br />
<br />
Via the [[AOLserver Public License]], viewable at http://aolserver.com/license/.<br />
<br />
----<br />
<br />
'''How does AOLserver performance compare to other major servers?'''<br />
<br />
[[Brady Wetherington]] says: On Unix, AOLserver can generate many, many dynamic pages very quickly and reliably. It also has some special code paths designed to speed up processing of static pages (fastpath), though I don't use that very much, personally. Along with the database connection pools, it's definitely one of the highest-performance web-based database systems I've used.<br />
<br />
<br />
'''How is it different from Apache HTTP Server?'''<br />
<br />
The current Apache HTTP Server<br />
* is part of / a project of the Apache Software Foundation. The process of development and decision making is working for years and accepted by all participants<br />
* allows to run applications in a process-pre-forking or multi-threaded environment by design<br />
* is the leading webserver, so it is widely known, accepted and supported<br />
* is itself a subproject accompanied by lots of well known other projects and frameworks (like Ant, Jakarta, Struts...)<br />
<br />
In contrast AOLserver<br />
* can do lots of use cases that are done with Apache modules with a few lines of TCL code (via registered filters and procs)<br />
* is bound to its multi-threaded architecture that has its own disadvantages, depending on what you want to do<br />
<br />
'''How is it different from <insert other webserver>?'''<br />
<br />
???<br />
<br />
----<br />
<br />
'''Where is AOLserver appropriate? Where is it not?'''<br />
<br />
It is not appropriate...<br />
* when you want to do virtual hosting for multiple customers. For static content, AOLserver is fine - you're just serving static content. For dynamic, server-side functionality, to get the level of privilege separation necessary, you'd have to run a separate nsd per customer to ensure that one customer can't access the content/data of another's. There are apparently some folks out there who have set up AOLserver just this way and are doing just this.<br />
* when the code you want to use is not thread-safe (and you are not able to change that)<br />
* when your main application makes heavy use of cgi-tools or other scripting languages like PHP or Phython (in general: where currently no active dedicated maintainer for corresponding modules is known)<br />
* when you need backup of a large world wide community that uses tools, modules and code you can find and read in every single computer magazine. AOLserver and TCL are niche products, which only means they are not sexy to the broad audience, but are used intensively by a sophisticated, intelligent minority<br />
* when you know you would need more than one day to convince your customer to use it (in other words: if you use technology the first time don't let your most important customer be the beta tester)<br />
<br />
It is appropriate...<br />
* when you want to make maximum use of your machines hardware ressources: AOLserver is a highly configurable beast that allows you to run big websites<br />
* when you plan to run a website that makes heavy use of one or more databases (using pooled connections)<br />
* when you want to cache lots or all of your static files (.html,.gif,.css.,.js ...) in your servers memory (via modules fastpath and nscache)<br />
* when you like the good feeling of running and coding your apps on a well-tested multi-threaded server architecture. The server never has been a process-forking one.<br />
<br />
<br />
The idea here is if you know your requirements and your scope is fairly stable and you feel comfortable you can predict the future, and if all signs point to the app. remaining small-to-medium in usage/traffic, then pick whatever platform or technology you like the best -- it really won't make a difference. But, if you think that it's a very real possibility you'll need<br />
to scale up capacity to meet growing demand/traffic, possibly indefinitely, then yes, the hidden cost of re-architecting or migrating to a different technology can be a killer when you have to use the words "sunk cost" to describe the originally developed system. In that case, you may be better off starting with implementing with AOLserver, as its performance "ceiling" so to speak is higher than other technologies. (TODO: Benchmarks demonstrating this empirically?)<br />
<br />
----<br />
<br />
'''How do I get started with AOLserver?'''<br />
<br />
<need to link to a newbie guide HOWTO><br />
<br />
----<br />
<br />
'''How can I learn more about AOLserver?'''<br />
<br />
Start by reading the [[Documentation]], which is still a work-in-progress.<br />
<br />
----<br />
<br />
'''"package require" doesn't work! What's wrong?'''<br />
<br />
Here's the relevant portion of a message [[Dossy Shiobara]] sent to the AOLserver mailing list back on 16 June 2000:<br />
<br />
set tcl_library [file join $tcl_pkgPath tcl${tcl_version}]<br />
source [file join $tcl_library init.tcl]<br />
<br />
package require works like a charm after that :-)<br />
<br />
There you have it. Perhaps, some day, this won't be a necessary step. But, in the meantime ...<br />
<br />
''As of AOLserver 4.0 and perhaps even a late version of 3.5.x, this step should no longer be necessary.''<br />
<br />
----<br />
<br />
'''"ns_set update [ns_conn outputheaders $conn] Content-Type {application/x-tcl}" does not work in .adp files as I wish. The server always returns two copies of the Content-Type header, one as application/x-tcl, another as text/html and clients(galeon, tcl http package) always use the second. How do I remove the second Content-Type?'''<br />
<br />
Good question -- this is really a bug that needs to be fixed in the server code itself.<br />
<br />
----<br />
<br />
'''How can I get Tclet scripts served from AOLserver to run inside the Tcl Plugin?'''<br />
<br />
Someone asks: ''I have an aolserver for OpenACS. I installed Tcl Plugin which works well with classic Tclets on Tcl Plugin Home Pages. But with Aolserver, it doesn't work.... Do you know the answer of this?''<br />
<br />
----<br />
<br />
'''How can I compile AOLserver on HP-UX, both 10.20 and 11.x?'''<br />
<br />
[[Dossy]]: Good question. If I had easy access to HP-UX machines, I'd try it myself. AOLserver 4.x should hopefully build on HP-UX without any changes, but I'm only guessing.<br />
<br />
HPUX doesn't implement a lot of BSD/POSIX IPC functions, or so I hear.<br />
<br />
----<br />
<br />
'''I'm getting an error compiling AOLserver about POLLIN, POLLOUT and POLLPRI being redefined. What's wrong?'''<br />
<br />
AOLserver requires that the "configure" script be run using the GNU C (gcc) compiler. Try running the configure script like this:<br />
<br />
$ CC=gcc ./configure --args...<br />
<br />
----<br />
<br />
'''Does AOLserver support HTTP Keep-Alive? I'm sending a HTTP/1.1 request via httperf and AOLserver isn't doing Keep-Alive like Apache does! What's wrong?'''<br />
<br />
Actually, nothing is wrong. You just need to tell httperf to include the headers that tell AOLserver to expect multiple requests per connection. Add '--add_header "Connection: Keep-Alive\n"' to your httperf request. <br />
<br />
The issue is that Apache and AOLserver chose opposite default behaviors when interpretting [http://www.ietf.org/rfc/rfc2068.txt RFC 2068 section 8.1.2.1]:<br />
<br />
An HTTP/1.1 server MAY assume that a HTTP/1.1 client intends to<br />
maintain a persistent connection unless a Connection header including<br />
the connection-token "close" was sent in the request. If the server<br />
chooses to close the connection immediately after sending the<br />
response, it SHOULD send a Connection header including the<br />
connection-token close.<br />
<br />
An HTTP/1.1 client MAY expect a connection to remain open, but would<br />
decide to keep it open based on whether the response from a server<br />
contains a Connection header with the connection-token close. In case<br />
the client does not want to maintain a connection for more than that<br />
request, it SHOULD send a Connection header including the<br />
connection-token close.<br />
<br />
The key here is "MAY" -- AOLserver (currently, as of 4.0.10) chooses not to assume a Keep-Alive connection unless the client explicitly requests it by sending "Connection: Keep-Alive" in the HTTP request header. This may change in the future (HTTP/1.1 requests default to Keep-Alive unless the client explicitly sends "Connection: close" -- apparently this is how Apache works).<br />
<br />
----<br />
<br />
[[Category Documentation]]</div>Cavemanhttps://panoptic.com/mediawiki/aolserver/index.php?title=Ns_job&diff=4634Ns job2005-12-14T14:44:22Z<p>Caveman: /* removed spam */</p>
<hr />
<div>{{manpage|ns_job}}<br />
<br />
'''NAME'''<br />
<br />
: ns_job - Implement job queues and thread pools for evaluating Tcl scripts<br />
<br />
'''SYNOPSIS'''<br />
<br />
: '''ns_job''' ''option ?arg arg ...?''<br />
<br />
'''DESCRIPTION'''<br />
<br />
: '''ns_job''' manages a thread pool and a set of named "queues". Queues have a max number of threads and when the current number of running thread reaches "max" then jobs are queued. New threads are created when there are less than maxthread number of idle threads.<br />
<br />
: This command provides a means for queueing Tcl scripts for evaluation by a pool of threads. The legal ''option''s (which may be abbreviated) are:<br />
* '''ns_job create''' ''?-desc description? queueId ?maxthreads?''<br />
<br />
: Create a new job queue called ''queueId''. If ''maxthreads'' is not specified, then the default of 4 is used.<br />
* '''ns_job queue''' ''?-detached?'' queueId script<br />
<br />
: Add a new job to the queue. If there are less than maxthreads current running then the job will be started. If there are maxthreads currently running then this new job will be queued.<br />
<br />
: If ''-detached'', then the job will be claned up when it completes; no wait will be necessary.<br />
<br />
: The new job's ID is returned.<br />
* '''ns_job wait''' ''?-timeout seconds:microseconds?'' queueId jobId<br />
<br />
: Wait for the specified queued or running job to finish. '''ns_job wait''' returns the results of the script.<br />
<br />
: An error is thrown if the specified timeout period is reached.<br />
* '''ns_job waitany''' ''?-timeout seconds:microseconds?'' queueId<br />
<br />
: Wait for any job on the queue complete.<br />
<br />
: An error is thrown if the specified timeout period is reached.<br />
* '''ns_job cancel''' queueId jobId<br />
<br />
: Remove the specified job from the queue. If the job is currently running, then the job will be removed from the queue when it completes.<br />
<br />
: 1 (true) is returned if the job is currently running and can not be cancelled.<br />
* '''ns_job delete''' queueId<br />
<br />
: Request that the specified queue be deleted. The queue will only be deleted when all jobs are removed.<br />
* '''ns_job jobs''' queueId<br />
<br />
: Return a list of the job IDs.<br />
* '''ns_job queues'''<br />
<br />
: Returns a list of the queue IDs.<br />
* '''ns_job threadlist'''<br />
<br />
: Returns a list of the thread pool's fields.<br />
<br />
: '''maxthreads''' - Max number of threads for all the queues in the thread pool.<br />
<br />
: '''numthreads''' - Number of allocated threads.<br />
<br />
: '''numidle''' - Number of currently idle threads.<br />
<br />
: '''req stop''' - The thread pools is being stopped. This probably means that the server is shutting down.<br />
* '''ns_job queuelist'''<br />
<br />
: Returns a list of the queues. A queue has the following fields:<br />
<br />
: '''name''' - Name of the queue.<br />
<br />
: '''desc''' - Description of the queue.<br />
<br />
: '''maxthreads''' - Max number of threads to run for this queue.<br />
<br />
: '''numrunning''' - Number of currently running jobs in this queue.<br />
<br />
: '''REQ delete''' - Someone requested this queue be deleted. Queue will not be deleted until all the jobs on the queue are removed.<br />
* '''ns_job joblist''' queueId<br />
<br />
: Returns a list the jobs in the specified queue. A job has the following fields:<br />
<br />
: '''id''' - Job's ID<br />
<br />
: '''state''' - The state of the job. The return values are as follows:<br />
<br />
: scheduled - The job is scheduled to run.<br />
<br />
: running - The job is currently running.<br />
<br />
: done - The job has completed.<br />
<br />
: '''results''' - If the job has completed, then this field will contain the results. If the job is running or scheduled to run, then this will contain the script.<br />
<br />
: '''code''' - When the job is done, this will contain the return code. Return codes are ''TCL_OK'', ''TCL_ERROR'', ''TCL_RETURN'', ''TCL_BREAK'', ''TCL_CONTINUE''.<br />
<br />
: '''type''' - The type of job. A job's return value is ''nondetached'' or ''detached''.<br />
<br />
: '''req''' - The job is required. Return values are ''none'', ''wait'', ''cancel''.<br />
* '''ns_job genid'''<br />
<br />
: Generate a new unique ID. This new ID can be used as the queue ID without conflicting with any other queue ID.<br />
<br />
<br />
'''EXAMPLES'''<br />
<br />
'''SEE ALSO'''<br />
<br />
<br />
[[Category:Core Tcl API]]</div>Cavemanhttps://panoptic.com/mediawiki/aolserver/index.php?title=Talk:Web_Applications_for_AOLserver&diff=4632Talk:Web Applications for AOLserver2005-12-13T17:44:21Z<p>Caveman: AJAX discussion</p>
<hr />
<div>Before we can willy-nilly go off and implement one or more of these things, shouldn't there be some common model of application, user, role, etc, that should be defined so that there is at least the potential of some or all of the applications being able to co-exist? For example, to-do list, calendar, web-mail, if they all used a common model there would be the potential to tie them all in together (e.g. OSSWEB).<br />
<br />
== AJAX discussion ==<br />
<br />
Has much been done in the area of AJAX implementations using AOLserver? Yes, it is another one of those buzz words full of promise, etc, and also full of drawbacks that people don't like to talk about. Yet it would be interesting to see what kind of performance AOLserver can do serving thousands of pages with thousands more AJAX requests. I would guess very good. The requests can probably be parsed by hand using ns_xml, but perhaps we could provide even simpler hooks for applications to use.</div>Cavemanhttps://panoptic.com/mediawiki/aolserver/index.php?title=User_talk:Caveman&diff=4631User talk:Caveman2005-12-13T14:56:29Z<p>Caveman: </p>
<hr />
<div>Hi, and welcome to the wiki! If you don't mind me asking, what's your full name (or do you want to remain anonymous)? Are you also subscribed to the [http://aolserver.com/lists.php AOLSERVER mailing list]? Some of us also hang out on [http://aolserver.com/chat/ IRC and chat] (you can also access the chat via AIM, but most folks use IRC).<br />
<br />
If you have any questions or concerns, don't hesitate to contact me. Thanks! ''-- [[User:Dossy|Dossy]] 07:13, 3 December 2005 (EST)''<br />
<br />
----<br />
<br />
Why does it seem like you're avoiding Tcl? Your recent wiki edits have been focused around other languages in AOLserver other than Tcl, like Lua, PHP and Ruby. Why? You will really never get the kind of performance out of Perl, PHP or Ruby as you will Tcl, because Tcl is suitable for embedding in a multi-threaded application where Perl, PHP and Ruby aren't. (I don't know enough about Lua to say one way or the other.) So, if you still want to use those other languages, then you probably don't care about performance at the high end, in which case, you probably don't need to use AOLserver, either. In the small, any web server will be more than adequate on modern hardware to serve a few hundred pages here and there. It's when you start getting into the few hundred per second arena where AOLserver has the opportunity to shine. ''-- [[User:Dossy|Dossy]] 07:46, 10 December 2005 (EST)''<br />
<br />
* Not at all -- I'm looking at other languages simply from the point of view of seeing how AOLServer modules are built at all. It has been a while since I did any heavy lifting with C, and I felt that tinkering with the module code would be a good refresher. Just scratching an itch. I use TCL heavily every day at work, and have no real knowledge of Lua either, it just seemed an opportune target to use when examining the general AOLServer module layer. --[[Caveman]] 12:23, 12 December 2005 (EST) <br />
<br />
** Okay, cool. FYI, "AOLserver" is capitalized just like that, not "AOLServer" -- I'm picking nits, but the consistency is important to me. Thanks. :-) ''-- [[User:Dossy|Dossy]] 12:41, 12 December 2005 (EST)''<br />
<br />
*** Ack. I've been doing that on a ton of pages -- my mistake, I will try to use the correct capitalisation. --[[User:Caveman|Caveman]] 12:43, 12 December 2005 (EST)<br />
<br />
== towards a data and authentication layer ==<br />
<br />
It is possible that similar exists elsewhere (non-OpenACS) but I enjoy framework construction anyway. Services provided:<br />
# authentication (password check)<br />
# sequences<br />
# data layer<br />
<br />
----<br />
<br />
Authentication/Authorization config (nsz):<br />
<pre><br />
# config: "/security/password/expression"<br />
# {ns_sha1 [ns_md5 [lindex $args 0]] [lindex $args 1]}<br />
# config: "/security/password/query"<br />
# {select password, salt from users where name='[ns_dbquoteval [lindex $args 0]]'}<br />
# config: "/security/salt/length" "8"<br />
# config: "/security/salt/dictionary" "0123456789abcdefghijkl..."<br />
</pre><br />
<br />
Basically the "expression" is used in a function, '''nsz_password''' to format a given clear-text password (varargs "args" to allow additional arguments to the function). The first argument is always the password.<br />
<br />
The "query" is executed as part of password-based authentication. The form handler reaches '''nsz_auth "myname" "mypassword"''' and the query is executed using the input list "myname". All row data beyond the first column, which must always be the password, is appended to the input password "mypassword" to produce the hash/salted/hash input "xpassword". This input "xpassword" is compared with the result of the returned value for the first column from the database query. If there is a match, password authentication succeeds for the user.<br />
<br />
Examples:<br />
<pre><br />
nsz_auth "sam" "correctpassword"<br />
# Query returns "sadf8vcx8vxasd7f7...","asduf7z6dfa..."<br />
# Expression eval for input passes "correctpassword","asduf7z6dfa..." and returns "sadf8vcx8vxasd7f7..."<br />
# Return value matches query<br />
# nsz_auth returns "sam"<br />
<br />
nsz_auth "sam" "badpassword"<br />
# Query returns "sadf8vcx8vxasd7f7...","asduf7z6dfa..."<br />
# Expression eval for input passes "badpassword","asduf7z6dfa..." and returns "yyzkfosd232cx7c..."<br />
# Return value does not match query<br />
# nsz_auth raises error "bad password"<br />
</pre><br />
<br />
Different configurations could use simple clear-text passwords, no salt, etc, simply by changing their configuration:<br />
<pre><br />
# config: "nsz/security/password/expression"<br />
# {lindex $args 0}<br />
# config: "nsz/security/password/query"<br />
# {select password from users where name='[ns_dbquoteval [lindex $args 0]]'}<br />
</pre><br />
<br />
The above would be the default configuration. For salt, the default would be size of 8 and dictionary of alphanumerics.<br />
<br />
Function '''nsz_salt''' can take 0, 1, or 2 arguments and returns the generated salt. The first argument is the length of the salt, defaults to config value. The second argument is the dictionary for the salt, default to config value.<br />
<br />
'''Question:''' How to make "users" table configurable? What about configuring which database pool to use? What about multiple authentication realms?<br />
<br />
----<br />
<br />
Sequences configuration should be as simple as specifying the database pool to use (default by default), the name of the sequence table, the size of the sequence chunk to claim when the local cache runs out of sequence numbers, and the number of retries before error during chunk claim. It could however be more complex, to specify the column names for the "name" and "value" of the sequence.<br />
<br />
Config:<br />
<pre><br />
# config: "nso/sequence/default/poolname" (default by default)<br />
# config: "nso/sequence/default/size" "100"<br />
# config: "nso/sequence/default/retry" "5"<br />
# config: "nso/sequence/default/table" "sequences_table"<br />
# config: "nso/sequence/default/name" "name_field"<br />
# config: "nso/sequence/default/value" "value_field"<br />
</pre><br />
<br />
Sequence defaults could be over-written per-sequence in similar fashion.<br />
<br />
Example usage:<br />
<pre><br />
set nextId [nso_sequence next "my_seq_name"]<br />
# returns 53 or error if fail<br />
</pre><br />
<br />
The function '''nso_sequence''' would thread-safe return the next sequence number it had available in its local nsv data, or if not available, claim the next chunk of 100 sequences numbers from the database:<br />
<pre><br />
# select value_field from sequences_table where name_field='my_seq_name'<br />
# result is 125, attempt to claim 100 values<br />
# update cave_sequences set value=225 where name_field='my_seq_name' and value_field=125<br />
</pre><br />
<br />
This would be retried up to ''5'' times.<br />
<br />
----<br />
<br />
Data layer notes:<br />
<br />
Config would map names like "users" to database pools and table names. Default would be default database pool and identity table name.<br />
<br />
Example usage:<br />
<pre><br />
# set nssValues [ns_set create]<br />
# ns_set update $nssValues "name" "sam"<br />
# ns_set update $nssValues "password" "mypassword"<br />
# ns_set put $nssValues "mail" "sam@caveman.org"<br />
# set nssUserKey [nso_row create "users" $nssValues]<br />
# set nssNewValues [ns_set create]<br />
# ns_set put $nssNewValues "mail" "samuelmb@gmail.com"<br />
# nso_row update "users" $nssUserKey $nssNewValues<br />
</pre><br />
<br />
Using ns_set instead of a model type-checking "nso_set" at least for now for simplicity and it would be the simple case.<br />
<br />
Additional config allows for data transforms:<br />
<pre><br />
# multi stage of filters and expressions:<br />
#<br />
# stage 0: accept-data-filter<br />
# e.g. "require a password is not null"<br />
# e.g. "require this integer be above zero"<br />
# e.g. "require id not be set"<br />
#<br />
# stage 1: transform-data-filter<br />
# config: expressions to apply to row:<br />
# e.g. "generate a salt"<br />
# ns_set update $nssData "salt" [nsz_salt]<br />
# e.g. "transform the password"<br />
# ns_set update $nssData "password" [nsz_password [ns_set get $nssData "password"] [ns_set get $nssData "salt"]]<br />
# e.g. "generate the next id from sequence"<br />
# ns_set update $nssData "id" [nso_sequence next "my_seq_name"]<br />
#<br />
# stage 2: veto-data-filter?<br />
#<br />
# allow multiple "inheritance" of data rules? or just defining rules that<br />
# can be referenced by multiple tables?<br />
</pre><br />
<br />
''very draft state''</div>Cavemanhttps://panoptic.com/mediawiki/aolserver/index.php?title=User_talk:Caveman&diff=4630User talk:Caveman2005-12-13T14:54:22Z<p>Caveman: </p>
<hr />
<div>Hi, and welcome to the wiki! If you don't mind me asking, what's your full name (or do you want to remain anonymous)? Are you also subscribed to the [http://aolserver.com/lists.php AOLSERVER mailing list]? Some of us also hang out on [http://aolserver.com/chat/ IRC and chat] (you can also access the chat via AIM, but most folks use IRC).<br />
<br />
If you have any questions or concerns, don't hesitate to contact me. Thanks! ''-- [[User:Dossy|Dossy]] 07:13, 3 December 2005 (EST)''<br />
<br />
----<br />
<br />
Why does it seem like you're avoiding Tcl? Your recent wiki edits have been focused around other languages in AOLserver other than Tcl, like Lua, PHP and Ruby. Why? You will really never get the kind of performance out of Perl, PHP or Ruby as you will Tcl, because Tcl is suitable for embedding in a multi-threaded application where Perl, PHP and Ruby aren't. (I don't know enough about Lua to say one way or the other.) So, if you still want to use those other languages, then you probably don't care about performance at the high end, in which case, you probably don't need to use AOLserver, either. In the small, any web server will be more than adequate on modern hardware to serve a few hundred pages here and there. It's when you start getting into the few hundred per second arena where AOLserver has the opportunity to shine. ''-- [[User:Dossy|Dossy]] 07:46, 10 December 2005 (EST)''<br />
<br />
* Not at all -- I'm looking at other languages simply from the point of view of seeing how AOLServer modules are built at all. It has been a while since I did any heavy lifting with C, and I felt that tinkering with the module code would be a good refresher. Just scratching an itch. I use TCL heavily every day at work, and have no real knowledge of Lua either, it just seemed an opportune target to use when examining the general AOLServer module layer. --[[Caveman]] 12:23, 12 December 2005 (EST) <br />
<br />
** Okay, cool. FYI, "AOLserver" is capitalized just like that, not "AOLServer" -- I'm picking nits, but the consistency is important to me. Thanks. :-) ''-- [[User:Dossy|Dossy]] 12:41, 12 December 2005 (EST)''<br />
<br />
*** Ack. I've been doing that on a ton of pages -- my mistake, I will try to use the correct capitalisation. --[[User:Caveman|Caveman]] 12:43, 12 December 2005 (EST)<br />
<br />
== towards a data and authentication layer ==<br />
<br />
It is possible that similar exists elsewhere (non-OpenACS) but I enjoy framework construction anyway. Services provided:<br />
# authentication (password check)<br />
# sequences<br />
# data layer<br />
<br />
----<br />
<br />
Authentication/Authorization config (nsz):<br />
<pre><br />
# config: "/security/password/expression"<br />
# {ns_sha1 [ns_md5 [lindex $args 0]] [lindex $args 1]}<br />
# config: "/security/password/query"<br />
# {select password, salt from users where name='[ns_dbquoteval [lindex $args 0]]'}<br />
# config: "/security/salt/length" "8"<br />
# config: "/security/salt/dictionary" "0123456789abcdefghijkl..."<br />
</pre><br />
<br />
Basically the "expression" is used in a function, '''nsz_password''' to format a given clear-text password (varargs "args" to allow additional arguments to the function). The first argument is always the password.<br />
<br />
The "query" is executed as part of password-based authentication. The form handler reaches '''nsz_auth "myname" "mypassword"''' and the query is executed using the input list "myname". All row data beyond the first column, which must always be the password, is appended to the input password "mypassword" to produce the hash/salted/hash input "xpassword". This input "xpassword" is compared with the result of the returned value for the first column from the database query. If there is a match, password authentication succeeds for the user.<br />
<br />
Examples:<br />
<pre><br />
nsz_auth "sam" "correctpassword"<br />
# Query returns "sadf8vcx8vxasd7f7...","asduf7z6dfa..."<br />
# Expression eval for input passes "correctpassword","asduf7z6dfa..." and returns "sadf8vcx8vxasd7f7..."<br />
# Return value matches query<br />
# nsz_auth returns "sam"<br />
<br />
nsz_auth "sam" "badpassword"<br />
# Query returns "sadf8vcx8vxasd7f7...","asduf7z6dfa..."<br />
# Expression eval for input passes "badpassword","asduf7z6dfa..." and returns "yyzkfosd232cx7c..."<br />
# Return value does not match query<br />
# nsz_auth raises error "bad password"<br />
</pre><br />
<br />
Different configurations could use simple clear-text passwords, no salt, etc, simply by changing their configuration:<br />
<pre><br />
# config: "nsz/security/password/expression"<br />
# {lindex $args 0}<br />
# config: "nsz/security/password/query"<br />
# {select password from users where name='[ns_dbquoteval [lindex $args 0]]'}<br />
</pre><br />
<br />
The above would be the default configuration. For salt, the default would be size of 8 and dictionary of alphanumerics.<br />
<br />
Function '''nsz_salt''' can take 0, 1, or 2 arguments and returns the generated salt. The first argument is the length of the salt, defaults to config value. The second argument is the dictionary for the salt, default to config value.<br />
<br />
'''Question:''' How to make "users" table configurable? What about configuring which database pool to use? What about multiple authentication realms?<br />
<br />
----<br />
<br />
Sequences configuration should be as simple as specifying the database pool to use (default by default), the name of the sequence table, the size of the sequence chunk to claim when the local cache runs out of sequence numbers, and the number of retries before error during chunk claim. It could however be more complex, to specify the column names for the "name" and "value" of the sequence.<br />
<br />
Config:<br />
<pre><br />
# config: "nso/sequence/default/poolname" (default by default)<br />
# config: "nso/sequence/default/size" "100"<br />
# config: "nso/sequence/default/retry" "5"<br />
# config: "nso/sequence/default/table" "sequences_table"<br />
# config: "nso/sequence/default/name" "name_field"<br />
# config: "nso/sequence/default/value" "value_field"<br />
</pre><br />
<br />
Sequence defaults could be over-written per-sequence in similar fashion.<br />
<br />
Example usage:<br />
<pre><br />
set nextId [nso_sequence next "my_seq_name"]<br />
# returns 53 or error if fail<br />
</pre><br />
<br />
The function '''nso_sequence''' would thread-safe return the next sequence number it had available in its local nsv data, or if not available, claim the next chunk of 100 sequences numbers from the database:<br />
<pre><br />
# select value_field from sequences_table where name_field='my_seq_name'<br />
# result is 125, attempt to claim 100 values<br />
# update cave_sequences set value=225 where name_field='my_seq_name' and value_field=125<br />
</pre><br />
<br />
This would be retried up to ''5'' times.<br />
<br />
----<br />
<br />
Data layer notes:<br />
<br />
Config would map names like "users" to database pools and table names. Default would be default database pool and identity table name.<br />
<br />
Example usage:<br />
<pre><br />
# set nssValues [ns_set create]<br />
# ns_set update $nssValues "name" "sam"<br />
# ns_set update $nssValues "password" "mypassword"<br />
# ns_set put $nssValues "mail" "sam@caveman.org"<br />
# set nssUserKey [nso_row create "users" $nssValues]<br />
# set nssNewValues [ns_set create]<br />
# ns_set put $nssNewValues "mail" "samuelmb@gmail.com"<br />
# nso_row update "users" $nssUserKey $nssNewValues<br />
</pre><br />
<br />
Using ns_set instead of a model type-checking "nso_set" at least for now for simplicity and it would be the simple case.<br />
<br />
Additional config allows for data transforms:<br />
<pre><br />
# multi stage of filters and expressions:<br />
#<br />
# stage 0: accept-data-filter<br />
# e.g. "require a password is not null"<br />
# e.g. "require this integer be above zero"<br />
# e.g. "require id not be set"<br />
# e.g. "generate a salt"<br />
#<br />
# stage 1: transform-data-filter<br />
# config: expressions to apply to row:<br />
# ns_set update $nssData "salt" [nsz_salt]<br />
# ns_set update $nssData "password" [nsz_password [ns_set get $nssData "password"] [ns_set get $nssData "salt"]]<br />
# ns_set put $nssData "id" [nso_sequence next $sName]<br />
#<br />
# stage 2: veto-data-filter?<br />
#<br />
# allow multiple "inheritance" of data rules? or just defining rules that<br />
# can be referenced by multiple tables?<br />
</pre><br />
<br />
''very draft state''</div>Cavemanhttps://panoptic.com/mediawiki/aolserver/index.php?title=User_talk:Caveman&diff=4629User talk:Caveman2005-12-13T14:53:11Z<p>Caveman: towards a data and authentication layer</p>
<hr />
<div>Hi, and welcome to the wiki! If you don't mind me asking, what's your full name (or do you want to remain anonymous)? Are you also subscribed to the [http://aolserver.com/lists.php AOLSERVER mailing list]? Some of us also hang out on [http://aolserver.com/chat/ IRC and chat] (you can also access the chat via AIM, but most folks use IRC).<br />
<br />
If you have any questions or concerns, don't hesitate to contact me. Thanks! ''-- [[User:Dossy|Dossy]] 07:13, 3 December 2005 (EST)''<br />
<br />
----<br />
<br />
Why does it seem like you're avoiding Tcl? Your recent wiki edits have been focused around other languages in AOLserver other than Tcl, like Lua, PHP and Ruby. Why? You will really never get the kind of performance out of Perl, PHP or Ruby as you will Tcl, because Tcl is suitable for embedding in a multi-threaded application where Perl, PHP and Ruby aren't. (I don't know enough about Lua to say one way or the other.) So, if you still want to use those other languages, then you probably don't care about performance at the high end, in which case, you probably don't need to use AOLserver, either. In the small, any web server will be more than adequate on modern hardware to serve a few hundred pages here and there. It's when you start getting into the few hundred per second arena where AOLserver has the opportunity to shine. ''-- [[User:Dossy|Dossy]] 07:46, 10 December 2005 (EST)''<br />
<br />
* Not at all -- I'm looking at other languages simply from the point of view of seeing how AOLServer modules are built at all. It has been a while since I did any heavy lifting with C, and I felt that tinkering with the module code would be a good refresher. Just scratching an itch. I use TCL heavily every day at work, and have no real knowledge of Lua either, it just seemed an opportune target to use when examining the general AOLServer module layer. --[[Caveman]] 12:23, 12 December 2005 (EST) <br />
<br />
** Okay, cool. FYI, "AOLserver" is capitalized just like that, not "AOLServer" -- I'm picking nits, but the consistency is important to me. Thanks. :-) ''-- [[User:Dossy|Dossy]] 12:41, 12 December 2005 (EST)''<br />
<br />
*** Ack. I've been doing that on a ton of pages -- my mistake, I will try to use the correct capitalisation. --[[User:Caveman|Caveman]] 12:43, 12 December 2005 (EST)<br />
<br />
== towards a data and authentication layer ==<br />
<br />
It is possible that similar exists elsewhere (non-OpenACS) but I enjoy framework construction anyway. Services provided:<br />
# authentication (password check)<br />
# sequences<br />
# data layer<br />
<br />
----<br />
<br />
Authentication/Authorization config (nsz):<br />
<pre><br />
# config: "/security/password/expression"<br />
# {ns_sha1 [ns_md5 [lindex $args 0]] [lindex $args 1]}<br />
# config: "/security/password/query"<br />
# {select password, salt from users where name='[ns_dbquoteval [lindex $args 0]]'}<br />
# config: "/security/salt/length" "8"<br />
# config: "/security/salt/dictionary" "0123456789abcdefghijkl..."<br />
</pre><br />
<br />
Basically the "expression" is used in a function, '''nsz_password''' to format a given clear-text password (varargs "args" to allow additional arguments to the function). The first argument is always the password.<br />
<br />
The "query" is executed as part of password-based authentication. The form handler reaches '''nsz_auth "myname" "mypassword"''' and the query is executed using the input list "myname". All row data beyond the first column, which must always be the password, is appended to the input password "mypassword" to produce the hash/salted/hash input "xpassword". This input "xpassword" is compared with the result of the returned value for the first column from the database query. If there is a match, password authentication succeeds for the user.<br />
<br />
Examples:<br />
<pre><br />
nsz_auth "sam" "correctpassword"<br />
# Query returns "sadf8vcx8vxasd7f7...","asduf7z6dfa..."<br />
# Expression eval for input passes "correctpassword","asduf7z6dfa..." and returns "sadf8vcx8vxasd7f7..."<br />
# Return value matches query<br />
# nsz_auth returns "sam"<br />
<br />
nsz_auth "sam" "badpassword"<br />
# Query returns "sadf8vcx8vxasd7f7...","asduf7z6dfa..."<br />
# Expression eval for input passes "badpassword","asduf7z6dfa..." and returns "yyzkfosd232cx7c..."<br />
# Return value does not match query<br />
# nsz_auth raises error "bad password"<br />
</pre><br />
<br />
Different configurations could use simple clear-text passwords, no salt, etc, simply by changing their configuration:<br />
<pre><br />
# config: "nsz/security/password/expression"<br />
# {lindex $args 0}<br />
# config: "nsz/security/password/query"<br />
# {select password from users where name='[ns_dbquoteval [lindex $args 0]]'}<br />
</pre><br />
<br />
The above would be the default configuration. For salt, the default would be size of 8 and dictionary of alphanumerics.<br />
<br />
Function '''nsz_salt''' can take 0, 1, or 2 arguments and returns the generated salt. The first argument is the length of the salt, defaults to config value. The second argument is the dictionary for the salt, default to config value.<br />
<br />
'''Question:''' How to make "users" table configurable? What about configuring which database pool to use?<br />
<br />
----<br />
<br />
Sequences configuration should be as simple as specifying the database pool to use (default by default), the name of the sequence table, the size of the sequence chunk to claim when the local cache runs out of sequence numbers, and the number of retries before error during chunk claim. It could however be more complex, to specify the column names for the "name" and "value" of the sequence.<br />
<br />
Config:<br />
<pre><br />
# config: "nso/sequence/default/poolname" (default by default)<br />
# config: "nso/sequence/default/size" "100"<br />
# config: "nso/sequence/default/retry" "5"<br />
# config: "nso/sequence/default/table" "sequences_table"<br />
# config: "nso/sequence/default/name" "name_field"<br />
# config: "nso/sequence/default/value" "value_field"<br />
</pre><br />
<br />
Sequence defaults could be over-written per-sequence in similar fashion.<br />
<br />
Example usage:<br />
<pre><br />
set nextId [nso_sequence next "my_seq_name"]<br />
# returns 53 or error if fail<br />
</pre><br />
<br />
The function '''nso_sequence''' would thread-safe return the next sequence number it had available in its local nsv data, or if not available, claim the next chunk of 100 sequences numbers from the database:<br />
<pre><br />
# select value_field from sequences_table where name_field='my_seq_name'<br />
# result is 125, attempt to claim 100 values<br />
# update cave_sequences set value=225 where name_field='my_seq_name' and value_field=125<br />
</pre><br />
<br />
This would be retried up to ''5'' times.<br />
<br />
----<br />
<br />
Data layer notes:<br />
<br />
Config would map names like "users" to database pools and table names. Default would be default database pool and identity table name.<br />
<br />
Example usage:<br />
<pre><br />
# set nssValues [ns_set create]<br />
# ns_set update $nssValues "name" "sam"<br />
# ns_set update $nssValues "password" "mypassword"<br />
# ns_set put $nssValues "mail" "sam@caveman.org"<br />
# set nssUserKey [nso_row create "users" $nssValues]<br />
# set nssNewValues [ns_set create]<br />
# ns_set put $nssNewValues "mail" "samuelmb@gmail.com"<br />
# nso_row update "users" $nssUserKey $nssNewValues<br />
</pre><br />
<br />
Using ns_set instead of a model type-checking "nso_set" at least for now for simplicity and it would be the simple case.<br />
<br />
Additional config allows for data transforms:<br />
<pre><br />
# multi stage of filters and expressions:<br />
#<br />
# stage 0: accept-data-filter<br />
# e.g. "require a password is not null"<br />
# e.g. "require this integer be above zero"<br />
# e.g. "require id not be set"<br />
# e.g. "generate a salt"<br />
#<br />
# stage 1: transform-data-filter<br />
# config: expressions to apply to row:<br />
# ns_set update $nssData "salt" [nsz_salt]<br />
# ns_set update $nssData "password" [nsz_password [ns_set get $nssData "password"] [ns_set get $nssData "salt"]]<br />
# ns_set put $nssData "id" [nso_sequence next $sName]<br />
#<br />
# stage 2: veto-data-filter?<br />
#<br />
# allow multiple "inheritance" of data rules? or just defining rules that<br />
# can be referenced by multiple tables?<br />
</pre><br />
<br />
''very draft state''</div>Cavemanhttps://panoptic.com/mediawiki/aolserver/index.php?title=Ns_dbquotevalue&diff=4626Ns dbquotevalue2005-12-13T14:14:50Z<p>Caveman: fixed double bracket (double single quote not fixed)</p>
<hr />
<div>Man page: http://aolserver.com/docs/tcl/ns_dbquotevalue.html<br />
<br />
----<br />
<br />
'''NAME'''<br />
<br />
: ns_dbquotevalue - Prepare a value string for inclusion in an SQL statement.<br />
<br />
'''SYNOPSIS'''<br />
<br />
: '''ns_dbquotevalue''' ''value ?type?''<br />
<br />
'''DESCRIPTION'''<br />
<br />
: This command prepares the string ''value'' for inclusion in an SQL statement. If ''value'' is "", ns_dbquotevalue will return the string "NULL". If ''value'' is not "", the returned value depends on ''type''. If ''type'' is one of: bigint, bit, decimal, double, float, int, integer, numeric, real, smallint, or tinyint, then ''value'' will be returned without modification. When ''type'' is any other string, or if ''type'' is omitted, ''value'' will be surrounded by single quotes, and any single quotes that it contains will be escaped by translation into two single quotes.<br />
<br />
'''EXAMPLES'''<br />
<br />
% ns_dbquotevalue ""<br />
NULL<br />
<br />
% ns_dbquotevalue 45.3 float<br />
45.3<br />
<br />
% ns_dbquotevalue "John's Car"<br />
'John''s Car'<br />
<br />
% set company "John's Cheese Factory"<br />
% ns_db dml $db "INSERT INTO companies (name) VALUES ([ns_dbquotevalue $company])"<br />
<br />
'''SEE ALSO'''<br />
<br />
: [[ns_dbquotename]]<br />
<br />
----<br />
<br />
[[Category Documentation]] - [[Category Core Tcl API]]</div>Cavemanhttps://panoptic.com/mediawiki/aolserver/index.php?title=Talk:Ns_dbquotevalue&diff=4625Talk:Ns dbquotevalue2005-12-13T14:14:24Z<p>Caveman: double single quotes in examples</p>
<hr />
<div>== double single quotes in examples ==<br />
<br />
there are errors in the examples: the double single quote is being hijacked by the wiki and turning the text into italic instead of showing the double single quote.</div>Cavemanhttps://panoptic.com/mediawiki/aolserver/index.php?title=Ns_set&diff=4621Ns set2005-12-13T04:04:11Z<p>Caveman: cleaned up double-brackets in code samples</p>
<hr />
<div>Man page: http://aolserver.com/docs/tcl/ns_set.html<br />
<br />
----<br />
<br />
'''NAME'''<br />
<br />
: ns_set - Manipulate sets of key-value pairs<br />
<br />
'''SYNOPSIS'''<br />
<br />
: '''ns_set''' ''option ?arg arg ...?''<br />
<br />
'''DESCRIPTION'''<br />
<br />
: This command is used to manipulate sets of key-value pairs or "fields". The fields in the set are ordered by number. The field numbers start at zero and increase by one, up to the total number of fields. An '''ns_set''' is actually a multiset - in other words, the same key can appear multiple times in the same set. This data structure is particularly useful for things like HTTP headers which have this same property.<br />
<br />
: The legal ''option''s (which may be abbreviated) are:<br />
* '''ns_set array''' ''setId''<br />
<br />
: Returns the contents of the ''setId'' in a string representation similar to Tcl's '''array get''' format. This is useful for converting an '''ns_set''' to an '''array''' or for iterating over the key-value pairs with '''foreach'''. Since '''ns_set'''s can contain the same key multiple times, converting an '''ns_set''' to an '''array''' can result in an array that is not exactly the same as the original '''ns_set''' as keys in an array are unique.<br />
* '''ns_set cleanup'''<br />
<br />
: Frees all sets in the current interp.<br />
* '''ns_set copy''' ''?-persist? setId''<br />
<br />
: Returns a new set that has the same name and contents as the set referenced in ''setId''. If ''-persist'' is specified, the new set will not be freed when the current transaction ends, and you can free it later with '''ns_set free'''. If ''-persist'' is not specified, the new set is automatically freed when the transaction ends.<br />
* '''ns_set cput''' ''setId key value''<br />
<br />
: Appends a new field to the set with ''key'' and ''value'', if the field does not already exist in the set. If the field already exists in the set, the set is unchanged. Returns the field number of the new field, or the field number of the existing field if it already exists in the set.<br />
* '''ns_set create''' ''?-persist? ?name? ?key? ?value? ...''<br />
* '''ns_set new''' ''?-persist? ?name? ?key? ?value? ...''<br />
<br />
: Allocates memory for a new set and returns the setId for the new set. If ''-persist'' is specified, the new set will not be freed when the current transaction ends, and you can free it later with '''ns_set free'''. If ''-persist'' is not specified, the new set is automatically freed when the transaction ends.<br />
* '''ns_set delete''' ''setId fieldNumber''<br />
<br />
: Deletes the field in the set at field number ''fieldNumber''.<br />
* '''ns_set delkey''' ''setId key''<br />
<br />
: Removes the first field in the set whose key is ''key''. Note that there could be multiple fields in the set with this key; this command only removes the first occurrence.<br />
* '''ns_set find''' ''setId key''<br />
<br />
: Returns the index of the first field in the specified ''setId'' whose ''key'' matches the specified key. Indexing starts at zero. If no matching fields are found, '''ns_set find''' returns -1.<br />
* '''ns_set free''' ''setId''<br />
<br />
: Frees the specified set. Sets must be explicitly freed with '''ns_set free''' if the ''-persist'' option was used when creating the set. Otherwise, sets are automatically freed when the transaction ends.<br />
* '''ns_set get''' ''setId key''<br />
<br />
: Returns the first value associated with ''key''. If ''key'' isn't in the set, an empty string is returned.<br />
* '''ns_set icput''' ''setId key value''<br />
<br />
: Case-insensitive counterpart of '''ns_set cput'''.<br />
* '''ns_set idelkey''' ''setId key''<br />
<br />
: Case-insensitive counterpart of '''ns_set delkey'''.<br />
* '''ns_set ifind''' ''setId key''<br />
<br />
: Case-insensitive counterpart of '''ns_set find'''.<br />
* '''ns_set iget''' ''setId key''<br />
<br />
: Case-insensitive counterpart of '''ns_set get'''.<br />
* '''ns_set isnull''' ''setId fieldNumber''<br />
<br />
: Returns 1 if the value of the field specified by ''fieldNumber'' is null and 0 if it is not. Note that an empty string is not the same as a null. '''ns_set isnull''' will return 0 if the value is an empty string.<br />
* '''ns_set iunique''' ''setId key''<br />
<br />
: Case-insensitive counterpart of '''ns_set unique'''.<br />
* '''ns_set key''' ''setId fieldNumber''<br />
<br />
: Returns the key for the field numbered ''fieldNumber''. This command is useful when looping through all the key-value pairs in the set in order.<br />
* '''ns_set list''' ''?-shared?''<br />
<br />
: Returns the list of all non-persistent '''ns_set'''s. If ''-shared'' is specified, this command returns only the list of persistent '''ns_set'''s.<br />
* '''ns_set merge''' ''high low''<br />
<br />
: Merges two sets. Any fields in the ''low'' set are appended to the ''high'' set if a field with the same key name does not already exist in the ''high'' set.<br />
* '''ns_set move''' ''to from''<br />
<br />
: Moves all fields from the ''from'' set to the end of the ''to'' set, leaving the ''from'' set a valid, empty set.<br />
* '''ns_set name''' ''setId''<br />
<br />
: Returns the name of the set. Returns an empty string if no name has been set.<br />
* '''ns_set print''' ''setId''<br />
<br />
: Prints the specified set to stderr which should go to the server log. This is useful for debugging, but '''ns_set array''' may be more useful in actual code.<br />
* '''ns_set put''' ''setId key value''<br />
<br />
: Appends a new field to the set with ''key'' and ''value''. Note that the field is appended so if a previous field has the same key as the new field, the previous field will be returned by '''ns_set get'''. The field number of the new field is returned.<br />
* '''ns_set size''' ''setId''<br />
<br />
: Returns the number of fields in the set.<br />
* '''ns_set split''' ''?-persist? setId ?splitChar?''<br />
<br />
: Splits one set into multiple sets based on the ''splitChar'' as described below and returns a Tcl list of IDs for the newly-allocated sets. It assumes that the keys in the source ''setId'' contain a specific character (''splitChar'') that can be used to separate the name of a new set and the key in the new set. The default ''splitChar'' is a period ".".<br />
* '''ns_set truncate''' ''setId fieldNumber''<br />
<br />
: Removes any fields with index ''fieldNumber'' or greater and frees any memory allocated for them.<br />
* '''ns_set unique''' ''setId key''<br />
<br />
: Returns 1 if the specified key is unique in the specified set and 0 if it is not. For example, a web browser could send multiple "Accept:" headers which would end up in the header set for the connection. '''ns_set unique''' would return 0 for the "Accept:" key, because there are multiple fields with the key "Accept:". The test for uniqueness is performed case-sensitively.<br />
* '''ns_set update''' ''setId key value''<br />
<br />
: Updates the first field in the specified set whose key is ''key'' and replaces its value with ''value''. This is equivalent to '''ns_set delkey''' followed by '''ns_set put''' if there is only one field with the key of ''key''.<br />
* '''ns_set value''' ''setId fieldNumber''<br />
<br />
: Returns the value of the set at field number ''fieldNumber''. This command is useful when looping through all the key-value pairs in the set.<br />
<br />
'''EXAMPLES'''<br />
<br />
% set mySet [ns_set create mySetName a b c d e f A Joe B John C Jeff]<br />
d0<br />
<br />
% ns_set size $mySet<br />
6<br />
<br />
% ns_set name $mySet<br />
mySetName<br />
<br />
% ns_set array $mySet<br />
a b c d e f A Joe B John C Jeff<br />
<br />
% ns_set get $mySet A<br />
Joe<br />
<br />
% ns_set iget $mySet a<br />
b<br />
<br />
% ns_set unique $mySet a<br />
1<br />
<br />
% ns_set iunique $mySet a<br />
0<br />
<br />
% ns_set truncate $mySet 3<br />
<br />
% ns_set print $mySet<br />
mySetName:<br />
a = b<br />
c = d<br />
e = f<br />
<br />
% ns_set update $mySet c "Hello World!"<br />
2<br />
<br />
% ns_set print $mySet<br />
mySetName:<br />
a = b<br />
e = f<br />
c = Hello World!<br />
<br />
% ns_set find $mySet c<br />
2<br />
<br />
% ns_set find $mySet nokey<br />
-1<br />
<br />
% ns_set delete $mySet 0<br />
<br />
% ns_set array $mySet<br />
e f c {Hello World!}<br />
<br />
<br />
% set anotherSet [ns_set create]<br />
d1<br />
<br />
% ns_set list<br />
d0 d1<br />
<br />
% ns_set put $anotherSet dog.food "Yummy dog food!"<br />
0<br />
<br />
% ns_set put $anotherSet cat.food "Yummy cat food!"<br />
1<br />
<br />
% ns_set print $anotherSet<br />
<Unamed set>:<br />
dog.food = Yummy dog food!<br />
cat.food = Yummy cat food!<br />
<br />
% set newSets [ns_set split $anotherSet]<br />
d2 d3<br />
<br />
<br />
% foreach s $newSets { ns_set print $s }<br />
dog:<br />
food = Yummy dog food!<br />
cat:<br />
food = Yummy cat food!<br />
<br />
% ns_set key $anotherSet 0<br />
dog.food<br />
<br />
% ns_set value $anotherSet 1<br />
Yummy cat food!<br />
<br />
% ns_set move $mySet $anotherSet<br />
d0<br />
<br />
% ns_set array $mySet<br />
e f c {Hello World!} dog.food {Yummy dog food!} cat.food {Yummy cat food!}<br />
<br />
% ns_set array $anotherSet<br />
<br />
% set thirdSet [ns_set new]<br />
d4<br />
<br />
% ns_set move $thirdSet $mySet<br />
d4<br />
<br />
% ns_set array $thirdSet<br />
e f c {Hello World!} dog.food {Yummy dog food!} cat.food {Yummy cat food!}<br />
<br />
% array set testArray [ns_set array $thirdSet]<br />
<br />
'''NOTES'''<br />
<br />
: The ns_set command currently reports that it accepts two additional subcommands, idelete and purge. These are both noops (idelete may be a mistake as delete is already case-irrelevant).<br />
<br />
: NULL values, distinct from the empty string, are useful when representing a database row as an ns_set. Currently, it is difficult to get a NULL value in an ns_set through the TCL API. You may get a NULL value in the set created by [[ns_parsequery]] or by omitting the last value when seeding the ns_set in the create/new subcommand, etc. It is possible to create NULL-valued fields through the C API.<br />
<br />
: ns_set is intended for relatively ''small'' amounts of data. (Keys are found by a ''linear'' search through the whole underlying C array.) If you stuff very large amounts of data into an ns_set, performance will be very poor - use a Tcl Array instead for that.<br />
<br />
'''SEE ALSO'''<br />
<br />
: [[ns_findset]]<br />
<br />
----<br />
<br />
[[Category Documentation]] - [[Category Core Tcl API]]</div>Cavemanhttps://panoptic.com/mediawiki/aolserver/index.php?title=AOLserver_4_on_Debian&diff=4611AOLserver 4 on Debian2005-12-12T17:54:55Z<p>Caveman: corrected capitalisation use of AOLserver</p>
<hr />
<div>Some quick and easy steps to getting AOLserver 4 up and running on Debian 3.1:<br />
<br />
<pre><br />
# install aolserver4<br />
apt-get install aolserver4<br />
<br />
# optional: to get ns.h and makefiles to build your own custom C or C++ modules<br />
apt-get install aolserver4-dev<br />
<br />
# optional: to get some potentially useful documentation, should you choose to read it<br />
apt-get install aolserver4-doc<br />
<br />
# optional: module: Tcl API for AOLserver Caches<br />
apt-get install aolserver4-nscache<br />
<br />
# optional: module that implements IMAP4 interface<br />
apt-get install aolserver4-nsimap<br />
<br />
# optional: module for LDAP<br />
apt-get install aolserver4-nsldap<br />
<br />
# optional: module: module for SSL mode -- beta module for OpenSSL<br />
apt-get install aolserver4-nsopenssl<br />
<br />
# optional: module: Postgres connector <br />
apt-get install aolserver4-nspostgres<br />
<br />
# optional: module: performs SHA1 hashes -- warning, the SHA1 hash it provides is not to spec<br />
apt-get install aolserver4-nssha1<br />
<br />
# optional: Module for XML support<br />
apt-get install aolserver4-nsxml<br />
</pre><br />
<br />
After installing the package(s) you want:<br />
<br />
<pre><br />
/etc/init.d/aolserver4 start<br />
</pre><br />
<br />
And you are running AOLserver. Congratulations. To make changes to your configuration file, visit:<br />
<br />
<pre><br />
/etc/aolserver4/aolserver4.tcl<br />
</pre><br />
<br />
To view your server log, visit:<br />
<br />
<pre><br />
/var/log/aolserver4/aolserver4.log<br />
</pre><br />
<br />
== See also ==<br />
<br />
* [[PostgreSQL on Debian]]<br />
* [[Configuring AOLserver 4 and PostgreSQL on Debian]]</div>Cavemanhttps://panoptic.com/mediawiki/aolserver/index.php?title=PostgreSQL_on_Debian&diff=4610PostgreSQL on Debian2005-12-12T17:46:11Z<p>Caveman: </p>
<hr />
<div>While not always a part of an AOLserver installation, the fact that AOLserver is known almost foremost for its ability to support massively concurrent accesses to its database pools imply that it would be helpful to have such a database installed.<br />
<br />
Some quick and easy steps to getting Postgresql up and running on Debian 3.1:<br />
<br />
<pre><br />
# install postgresql<br />
apt-get install postgresql<br />
<br />
# optional: to get some potentially useful documentation, should you choose to read it<br />
apt-get install postgresql-doc<br />
<br />
# optional: if you think you might be up for some postgresql hacking sometime<br />
apt-get install postgresql-dev<br />
<br />
# optional: useful contributed software includes some cryptographic hash functions<br />
apt-get install postgresql-contrib<br />
</pre><br />
<br />
After installing the package(s) you want:<br />
<br />
<pre><br />
/etc/init.d/postgresql start<br />
</pre><br />
<br />
And you are running Postgresql. Congratulations. To make changes to your configuration files, visit:<br />
<br />
<pre><br />
/etc/postgresql/<br />
</pre><br />
<br />
'''Recommended'''<br />
<br />
While everyone has their own preferences for how to administer and customize their database installation, there are at least a couple of post-install steps that come in very handy:<br />
<br />
* [http://www.debian-administration.org/articles/208] details importing the useful pgcrypto functions from postgresql-contrib into your template database:<br />
<pre><br />
root @ box # su postgres<br />
postgres @ box $ psql template1 < /usr/share/postgresql/contrib/pgcrypto.sql<br />
</pre><br />
<br />
* [http://dev.panopticsearch.com/postgres_microhowto.html] details setting a database password for the postgres user, and setting up socket connection permissions (which allows, among other things, AOLserver to connect to the database):<br />
<pre><br />
postgres @ box $ psql template1<br />
Welcome to psql, the PostgreSQL interactive terminal.<br />
<br />
Type: \copyright for distribution terms<br />
\h for help with SQL commands<br />
\? for help on internal slash commands<br />
\g or terminate with semicolon to execute query<br />
\q to quit<br />
<br />
template1=#<br />
<br />
# Set a password for the database-user postgres (while being logged into the database (e.g. template1)).<br />
<br />
template1=# ALTER USER postgres WITH PASSWORD 'topsecret';<br />
ALTER USER<br />
template1=#<br />
<br />
# Log out of the database (\q):<br />
<br />
template1=# \q<br />
postgres @ box $<br />
</pre><br />
<br />
== See also ==<br />
<br />
* [[AOLserver 4 on Debian]]<br />
* [[Configuring AOLserver 4 and PostgreSQL on Debian]]</div>Cavemanhttps://panoptic.com/mediawiki/aolserver/index.php?title=PostgreSQL_on_Debian&diff=4609PostgreSQL on Debian2005-12-12T17:45:51Z<p>Caveman: corrected capitalisation use of AOLserver</p>
<hr />
<div>While not always a part of an AOLserver installation, the fact that AOLserver is known almost foremost for its ability to support massively concurrent accesses to its database pools imply that it would be helpful to have such a database installed.<br />
<br />
Some quick and easy steps to getting Postgresql up and running on Debian 3.1:<br />
<br />
<pre><br />
# install postgresql<br />
apt-get install postgresql<br />
<br />
# optional: to get some potentially useful documentation, should you choose to read it<br />
apt-get install postgresql-doc<br />
<br />
# optional: if you think you might be up for some postgresql hacking sometime<br />
apt-get install postgresql-dev<br />
<br />
# optional: useful contributed software includes some cryptographic hash functions<br />
apt-get install postgresql-contrib<br />
</pre><br />
<br />
After installing the package(s) you want:<br />
<br />
<pre><br />
/etc/init.d/postgresql start<br />
</pre><br />
<br />
And you are running Postgresql. Congratulations. To make changes to your configuration files, visit:<br />
<br />
<pre><br />
/etc/postgresql/<br />
</pre><br />
<br />
'''Recommended'''<br />
<br />
While everyone has their own preferences for how to administer and customize their database installation, there are at least a couple of post-install steps that come in very handy:<br />
<br />
* [http://www.debian-administration.org/articles/208] details importing the useful pgcrypto functions from postgresql-contrib into your template database:<br />
<pre><br />
root @ box # su postgres<br />
postgres @ box $ psql template1 < /usr/share/postgresql/contrib/pgcrypto.sql<br />
</pre><br />
<br />
* [http://dev.panopticsearch.com/postgres_microhowto.html] details setting a database password for the postgres user, and setting up socket connection permissions (which allows, among other things, AOLServer to connect to the database):<br />
<pre><br />
postgres @ box $ psql template1<br />
Welcome to psql, the PostgreSQL interactive terminal.<br />
<br />
Type: \copyright for distribution terms<br />
\h for help with SQL commands<br />
\? for help on internal slash commands<br />
\g or terminate with semicolon to execute query<br />
\q to quit<br />
<br />
template1=#<br />
<br />
# Set a password for the database-user postgres (while being logged into the database (e.g. template1)).<br />
<br />
template1=# ALTER USER postgres WITH PASSWORD 'topsecret';<br />
ALTER USER<br />
template1=#<br />
<br />
# Log out of the database (\q):<br />
<br />
template1=# \q<br />
postgres @ box $<br />
</pre><br />
<br />
== See also ==<br />
<br />
* [[AOLserver 4 on Debian]]<br />
* [[Configuring AOLserver 4 and PostgreSQL on Debian]]</div>Cavemanhttps://panoptic.com/mediawiki/aolserver/index.php?title=Talk:How_to_set_up_PHP_under_AOLserver&diff=4608Talk:How to set up PHP under AOLserver2005-12-12T17:44:31Z<p>Caveman: corrected capitalisation use of AOLserver</p>
<hr />
<div>I cannot get php-5.1.1 to build with Debian 3.1 package of aolserver4 and aolserver4-dev (which is built with --prefix=/usr/lib/aolserver4):<br />
<br />
<pre><br />
sam@caveman:~/downloads/php.net/php-5.1.1$ ./configure --with-aolserver=/usr/lib/aolserver4<br />
loading cache ./config.cache<br />
...<br />
...<br />
<br />
Configuring SAPI modules<br />
checking for AOLserver support... /usr/lib/aolserver4<br />
configure: error: Please specify the path to the source distribution of AOLserver using --with-aolserver-src=DIR<br />
sam@caveman:~/downloads/php.net/php-5.1.1$<br />
</pre><br />
<br />
* ''I only ever tested this against PHP 4.3.7 -- I don't know what is required to make it work with PHP 5.1.1. If you figure it out, please update the page. -- [[User:Dossy|Dossy]] 12:05, 7 December 2005 (EST)''<br />
<br />
** I opened a PHP bug issue for this: [http://bugs.php.net/bug.php?id=35605] --[[User:Caveman|Caveman]] 14:05, 8 December 2005 (EST)<br />
<br />
*** This may be an issue more with the way Debian 3.1 installs AOLserver 4 than anything else. The "proper" PHP configure command should be:<br />
<pre><br />
./configure --with-aolserver=/path/to/installed/aolserver<br />
</pre><br />
<br />
Debian 3.1 configures AOLServer with a prefix of "/usr/lib/aolserver4". However, using this as the "/path/to/installed/aolserver" results in the same error and a request for "--with-aolserver-src".<br />
<br />
**** I configured and installed aolserver4 from source into "/home/sam/aolserver". PHP configure finally completed successfully. However, PHP compile still failed:<br />
<br />
<pre><br />
/bin/sh /home/sam/downloads/php.net/php-5.1.1/libtool --silent --preserve-dup-deps --mode=compile /home/sam/downloads/php.net/php-5.1.1/meta_ccld -Isapi/aolserver/ -I/home/sam/downloads/php.net/php-5.1.1/sapi/aolserver/ -DPHP_ATOM_INC -I/home/sam/downloads/php.net/php-5.1.1/include -I/home/sam/downloads/php.net/php-5.1.1/main -I/home/sam/downloads/php.net/php-5.1.1 -I/home/sam/aolserver/include -I/usr/include/libxml2 -I/home/sam/downloads/php.net/php-5.1.1/ext/date/lib -I/home/sam/downloads/php.net/php-5.1.1/TSRM -I/home/sam/downloads/php.net/php-5.1.1/Zend -D_REENTRANT -g -O2 -pthread -DZTS -prefer-non-pic -c /home/sam/downloads/php.net/php-5.1.1/sapi/aolserver/aolserver.c -o sapi/aolserver/aolserver.lo<br />
In file included from /home/sam/aolserver/include/ns.h:62,<br />
from /home/sam/downloads/php.net/php-5.1.1/sapi/aolserver/aolserver.c:49:<br />
/home/sam/aolserver/include/nsthread.h:125:17: tcl.h: No such file or directory<br />
</pre><br />
<br />
This was obviously an error finding "tcl.h". I manually edited the PHP "Makefile" and set:<br />
<pre><br />
EXTRA_INCLUDES = -I/usr/include/tcl8.4<br />
</pre><br />
<br />
This allowed PHP compilation to complete. The module loaded successfully and PHP scripts work as expected (see [http://caveman.org/phpinfo/ phpinfo output]). --[[User:Caveman|Caveman]] 19:05, 8 December 2005 (EST)<br />
<br />
----<br />
<br />
With trial and error, I was able to configure and compile against the Debian 3.1 packages as installed by default:<br />
<br />
<pre><br />
./configure --with-aolserver=/usr<br />
make "EXTRA_INCLUDES=-I/usr/include/tcl8.4 -I/usr/include/aolserver4"<br />
</pre><br />
<br />
== extending PHP to take advantage of AOLServer ==<br />
<br />
http://aolserver.org/docs/devel/c/api/c-ch3.htm#37064<br />
<br />
proposal: write a PHP extension to provide PHP functions to access AOLserver database pools (and perhaps other important features like shared memory).<br />
<br />
In other words, provide PHP functions:<br />
<br />
<pre><br />
ns_db_gethandle<br />
ns_db_select<br />
</pre><br />
<br />
And so on. It should be nearly trivial to do this, and give PHP on AOLserver a very powerful advantage over PHP on Apache.<br />
<br />
[http://www.webtechniques.com/archives/2001/01/junk/ Extending PHP By Sterling Hughes]<br />
<br />
<pre><br />
sam@caveman:~/downloads/php.net/php-5.1.1/ext$ ./ext_skel --extname=nsdb<br />
Creating directory nsdb<br />
Creating basic files: config.m4 config.w32 .cvsignore nsdb.c php_nsdb.h CREDITS EXPERIMENTAL tests/001.phpt nsdb.php [done].<br />
<br />
To use your new extension, you will have to execute the following steps:<br />
<br />
1. $ cd ..<br />
2. $ vi ext/nsdb/config.m4<br />
3. $ ./buildconf<br />
4. $ ./configure --[with|enable]-nsdb<br />
5. $ make<br />
6. $ ./php -f ext/nsdb/nsdb.php<br />
7. $ vi ext/nsdb/nsdb.c<br />
8. $ make<br />
<br />
Repeat steps 3-6 until you are satisfied with ext/nsdb/config.m4 and<br />
step 6 confirms that your module is compiled into PHP. Then, start writing<br />
code and repeat the last two steps as often as necessary.<br />
</pre></div>Cavemanhttps://panoptic.com/mediawiki/aolserver/index.php?title=User_talk:Caveman&diff=4607User talk:Caveman2005-12-12T17:43:03Z<p>Caveman: </p>
<hr />
<div>Hi, and welcome to the wiki! If you don't mind me asking, what's your full name (or do you want to remain anonymous)? Are you also subscribed to the [http://aolserver.com/lists.php AOLSERVER mailing list]? Some of us also hang out on [http://aolserver.com/chat/ IRC and chat] (you can also access the chat via AIM, but most folks use IRC).<br />
<br />
If you have any questions or concerns, don't hesitate to contact me. Thanks! ''-- [[User:Dossy|Dossy]] 07:13, 3 December 2005 (EST)''<br />
<br />
----<br />
<br />
Why does it seem like you're avoiding Tcl? Your recent wiki edits have been focused around other languages in AOLserver other than Tcl, like Lua, PHP and Ruby. Why? You will really never get the kind of performance out of Perl, PHP or Ruby as you will Tcl, because Tcl is suitable for embedding in a multi-threaded application where Perl, PHP and Ruby aren't. (I don't know enough about Lua to say one way or the other.) So, if you still want to use those other languages, then you probably don't care about performance at the high end, in which case, you probably don't need to use AOLserver, either. In the small, any web server will be more than adequate on modern hardware to serve a few hundred pages here and there. It's when you start getting into the few hundred per second arena where AOLserver has the opportunity to shine. ''-- [[User:Dossy|Dossy]] 07:46, 10 December 2005 (EST)''<br />
<br />
* Not at all -- I'm looking at other languages simply from the point of view of seeing how AOLServer modules are built at all. It has been a while since I did any heavy lifting with C, and I felt that tinkering with the module code would be a good refresher. Just scratching an itch. I use TCL heavily every day at work, and have no real knowledge of Lua either, it just seemed an opportune target to use when examining the general AOLServer module layer. --[[Caveman]] 12:23, 12 December 2005 (EST) <br />
<br />
** Okay, cool. FYI, "AOLserver" is capitalized just like that, not "AOLServer" -- I'm picking nits, but the consistency is important to me. Thanks. :-) ''-- [[User:Dossy|Dossy]] 12:41, 12 December 2005 (EST)''<br />
<br />
*** Ack. I've been doing that on a ton of pages -- my mistake, I will try to use the correct capitalisation. --[[User:Caveman|Caveman]] 12:43, 12 December 2005 (EST)</div>Cavemanhttps://panoptic.com/mediawiki/aolserver/index.php?title=User_talk:Dossy&diff=4604User talk:Dossy2005-12-12T17:23:28Z<p>Caveman: re: avoiding TCL</p>
<hr />
<div>== re: avoiding TCL ==<br />
<br />
Not at all -- I'm looking at other languages simply from the point of view of seeing how AOLServer modules are built at all. It has been a while since I did any heavy lifting with C, and I felt that tinkering with the module code would be a good refresher. Just scratching an itch. I use TCL heavily every day at work, and have no real knowledge of Lua either, it just seemed an opportune target to use when examining the general AOLServer module layer. --[[User:Caveman|Caveman]] 12:23, 12 December 2005 (EST)</div>Cavemanhttps://panoptic.com/mediawiki/aolserver/index.php?title=Talk:Embedding_a_new_programming_language_as_a_module&diff=4581Talk:Embedding a new programming language as a module2005-12-09T16:09:38Z<p>Caveman: apache mod_lua link</p>
<hr />
<div>Do you think any examples like:<br />
<pre><br />
Ns_Log(Debug, "opening lua state");<br />
</pre><br />
<br />
Would be useful here?<br />
<br />
----<br />
<br />
What about proper termination:<br />
<pre><br />
Ns_RegisterShutdown(MyLuaCleanup, ...);<br />
</pre><br />
<br />
----<br />
<br />
Also eventually the reader may need to learn about <pre>Ns_ConfigGetValue</pre> to complete more complex tasks.<br />
<br />
----<br />
<br />
I honestly don't know how to go about building or configuring a ".lua" extension handler. The full-fledged example I would look at (PyWX) is a great example of a C++ module, but it's a bit difficult for me to translate what's going on in PyWX to what I should do for Lua with a C module. I might be able to work out the extension handler portion, but getting Lua's "print" to output correctly might be tricky. -- --[[User:Caveman|Caveman]] 08:42, 6 December 2005 (EST)<br />
<br />
== apache mod_lua link ==<br />
<br />
There is an Apache "mod_lua" on Sourceforge that could be useful for a "real" nslua module developer:<br />
<br />
[http://sourceforge.net/projects/modlua/]<br />
<br />
[http://cvs.sourceforge.net/viewcvs.py/modlua/modlua/mod_lua.c?rev=1.3&view=auto]<br />
<br />
--[[User:Caveman|Caveman]] 11:09, 9 December 2005 (EST)</div>Cavemanhttps://panoptic.com/mediawiki/aolserver/index.php?title=Talk:Ruby&diff=4580Talk:Ruby2005-12-09T15:28:45Z<p>Caveman: /* Ruby on Rails on AOLServer? */</p>
<hr />
<div>== Ruby on Rails on AOLServer? ==<br />
<br />
Any thoughts or ideas on whether [http://www.rubyonrails.org Ruby on Rails] would work with the nsruby module? --[[User:Caveman|Caveman]] 10:28, 9 December 2005 (EST)</div>Cavemanhttps://panoptic.com/mediawiki/aolserver/index.php?title=Talk:Ruby&diff=4579Talk:Ruby2005-12-09T15:28:31Z<p>Caveman: Ruby on Rails on AOLServer?</p>
<hr />
<div>== Ruby on Rails on AOLServer? ==<br />
<br />
Any thoughts or ideas on whether [http://www.rubyonrails.org Ruby on Rails] would work with the nsruby module?</div>Cavemanhttps://panoptic.com/mediawiki/aolserver/index.php?title=Talk:How_to_set_up_PHP_under_AOLserver&diff=4578Talk:How to set up PHP under AOLserver2005-12-09T02:33:49Z<p>Caveman: /* extending PHP to take advantage of AOLServer */</p>
<hr />
<div>I cannot get php-5.1.1 to build with Debian 3.1 package of aolserver4 and aolserver4-dev (which is built with --prefix=/usr/lib/aolserver4):<br />
<br />
<pre><br />
sam@caveman:~/downloads/php.net/php-5.1.1$ ./configure --with-aolserver=/usr/lib/aolserver4<br />
loading cache ./config.cache<br />
...<br />
...<br />
<br />
Configuring SAPI modules<br />
checking for AOLserver support... /usr/lib/aolserver4<br />
configure: error: Please specify the path to the source distribution of AOLserver using --with-aolserver-src=DIR<br />
sam@caveman:~/downloads/php.net/php-5.1.1$<br />
</pre><br />
<br />
* ''I only ever tested this against PHP 4.3.7 -- I don't know what is required to make it work with PHP 5.1.1. If you figure it out, please update the page. -- [[User:Dossy|Dossy]] 12:05, 7 December 2005 (EST)''<br />
<br />
** I opened a PHP bug issue for this: [http://bugs.php.net/bug.php?id=35605] --[[User:Caveman|Caveman]] 14:05, 8 December 2005 (EST)<br />
<br />
*** This may be an issue more with the way Debian 3.1 installs AOLServer 4 than anything else. The "proper" PHP configure command should be:<br />
<pre><br />
./configure --with-aolserver=/path/to/installed/aolserver<br />
</pre><br />
<br />
Debian 3.1 configures AOLServer with a prefix of "/usr/lib/aolserver4". However, using this as the "/path/to/installed/aolserver" results in the same error and a request for "--with-aolserver-src".<br />
<br />
**** I configured and installed aolserver4 from source into "/home/sam/aolserver". PHP configure finally completed successfully. However, PHP compile still failed:<br />
<br />
<pre><br />
/bin/sh /home/sam/downloads/php.net/php-5.1.1/libtool --silent --preserve-dup-deps --mode=compile /home/sam/downloads/php.net/php-5.1.1/meta_ccld -Isapi/aolserver/ -I/home/sam/downloads/php.net/php-5.1.1/sapi/aolserver/ -DPHP_ATOM_INC -I/home/sam/downloads/php.net/php-5.1.1/include -I/home/sam/downloads/php.net/php-5.1.1/main -I/home/sam/downloads/php.net/php-5.1.1 -I/home/sam/aolserver/include -I/usr/include/libxml2 -I/home/sam/downloads/php.net/php-5.1.1/ext/date/lib -I/home/sam/downloads/php.net/php-5.1.1/TSRM -I/home/sam/downloads/php.net/php-5.1.1/Zend -D_REENTRANT -g -O2 -pthread -DZTS -prefer-non-pic -c /home/sam/downloads/php.net/php-5.1.1/sapi/aolserver/aolserver.c -o sapi/aolserver/aolserver.lo<br />
In file included from /home/sam/aolserver/include/ns.h:62,<br />
from /home/sam/downloads/php.net/php-5.1.1/sapi/aolserver/aolserver.c:49:<br />
/home/sam/aolserver/include/nsthread.h:125:17: tcl.h: No such file or directory<br />
</pre><br />
<br />
This was obviously an error finding "tcl.h". I manually edited the PHP "Makefile" and set:<br />
<pre><br />
EXTRA_INCLUDES = -I/usr/include/tcl8.4<br />
</pre><br />
<br />
This allowed PHP compilation to complete. The module loaded successfully and PHP scripts work as expected (see [http://caveman.org/phpinfo/ phpinfo output]). --[[User:Caveman|Caveman]] 19:05, 8 December 2005 (EST)<br />
<br />
----<br />
<br />
With trial and error, I was able to configure and compile against the Debian 3.1 packages as installed by default:<br />
<br />
<pre><br />
./configure --with-aolserver=/usr<br />
make "EXTRA_INCLUDES=-I/usr/include/tcl8.4 -I/usr/include/aolserver4"<br />
</pre><br />
<br />
== extending PHP to take advantage of AOLServer ==<br />
<br />
http://aolserver.org/docs/devel/c/api/c-ch3.htm#37064<br />
<br />
proposal: write a PHP extension to provide PHP functions to access AOLServer database pools (and perhaps other important features like shared memory).<br />
<br />
In other words, provide PHP functions:<br />
<br />
<pre><br />
ns_db_gethandle<br />
ns_db_select<br />
</pre><br />
<br />
And so on. It should be nearly trivial to do this, and give PHP on AOLServer a very powerful advantage over PHP on Apache.<br />
<br />
[http://www.webtechniques.com/archives/2001/01/junk/ Extending PHP By Sterling Hughes]<br />
<br />
<pre><br />
sam@caveman:~/downloads/php.net/php-5.1.1/ext$ ./ext_skel --extname=nsdb<br />
Creating directory nsdb<br />
Creating basic files: config.m4 config.w32 .cvsignore nsdb.c php_nsdb.h CREDITS EXPERIMENTAL tests/001.phpt nsdb.php [done].<br />
<br />
To use your new extension, you will have to execute the following steps:<br />
<br />
1. $ cd ..<br />
2. $ vi ext/nsdb/config.m4<br />
3. $ ./buildconf<br />
4. $ ./configure --[with|enable]-nsdb<br />
5. $ make<br />
6. $ ./php -f ext/nsdb/nsdb.php<br />
7. $ vi ext/nsdb/nsdb.c<br />
8. $ make<br />
<br />
Repeat steps 3-6 until you are satisfied with ext/nsdb/config.m4 and<br />
step 6 confirms that your module is compiled into PHP. Then, start writing<br />
code and repeat the last two steps as often as necessary.<br />
</pre></div>Cavemanhttps://panoptic.com/mediawiki/aolserver/index.php?title=Talk:How_to_set_up_PHP_under_AOLserver&diff=4577Talk:How to set up PHP under AOLserver2005-12-09T02:21:41Z<p>Caveman: /* extending PHP to take advantage of AOLServer */ added link</p>
<hr />
<div>I cannot get php-5.1.1 to build with Debian 3.1 package of aolserver4 and aolserver4-dev (which is built with --prefix=/usr/lib/aolserver4):<br />
<br />
<pre><br />
sam@caveman:~/downloads/php.net/php-5.1.1$ ./configure --with-aolserver=/usr/lib/aolserver4<br />
loading cache ./config.cache<br />
...<br />
...<br />
<br />
Configuring SAPI modules<br />
checking for AOLserver support... /usr/lib/aolserver4<br />
configure: error: Please specify the path to the source distribution of AOLserver using --with-aolserver-src=DIR<br />
sam@caveman:~/downloads/php.net/php-5.1.1$<br />
</pre><br />
<br />
* ''I only ever tested this against PHP 4.3.7 -- I don't know what is required to make it work with PHP 5.1.1. If you figure it out, please update the page. -- [[User:Dossy|Dossy]] 12:05, 7 December 2005 (EST)''<br />
<br />
** I opened a PHP bug issue for this: [http://bugs.php.net/bug.php?id=35605] --[[User:Caveman|Caveman]] 14:05, 8 December 2005 (EST)<br />
<br />
*** This may be an issue more with the way Debian 3.1 installs AOLServer 4 than anything else. The "proper" PHP configure command should be:<br />
<pre><br />
./configure --with-aolserver=/path/to/installed/aolserver<br />
</pre><br />
<br />
Debian 3.1 configures AOLServer with a prefix of "/usr/lib/aolserver4". However, using this as the "/path/to/installed/aolserver" results in the same error and a request for "--with-aolserver-src".<br />
<br />
**** I configured and installed aolserver4 from source into "/home/sam/aolserver". PHP configure finally completed successfully. However, PHP compile still failed:<br />
<br />
<pre><br />
/bin/sh /home/sam/downloads/php.net/php-5.1.1/libtool --silent --preserve-dup-deps --mode=compile /home/sam/downloads/php.net/php-5.1.1/meta_ccld -Isapi/aolserver/ -I/home/sam/downloads/php.net/php-5.1.1/sapi/aolserver/ -DPHP_ATOM_INC -I/home/sam/downloads/php.net/php-5.1.1/include -I/home/sam/downloads/php.net/php-5.1.1/main -I/home/sam/downloads/php.net/php-5.1.1 -I/home/sam/aolserver/include -I/usr/include/libxml2 -I/home/sam/downloads/php.net/php-5.1.1/ext/date/lib -I/home/sam/downloads/php.net/php-5.1.1/TSRM -I/home/sam/downloads/php.net/php-5.1.1/Zend -D_REENTRANT -g -O2 -pthread -DZTS -prefer-non-pic -c /home/sam/downloads/php.net/php-5.1.1/sapi/aolserver/aolserver.c -o sapi/aolserver/aolserver.lo<br />
In file included from /home/sam/aolserver/include/ns.h:62,<br />
from /home/sam/downloads/php.net/php-5.1.1/sapi/aolserver/aolserver.c:49:<br />
/home/sam/aolserver/include/nsthread.h:125:17: tcl.h: No such file or directory<br />
</pre><br />
<br />
This was obviously an error finding "tcl.h". I manually edited the PHP "Makefile" and set:<br />
<pre><br />
EXTRA_INCLUDES = -I/usr/include/tcl8.4<br />
</pre><br />
<br />
This allowed PHP compilation to complete. The module loaded successfully and PHP scripts work as expected (see [http://caveman.org/phpinfo/ phpinfo output]). --[[User:Caveman|Caveman]] 19:05, 8 December 2005 (EST)<br />
<br />
----<br />
<br />
With trial and error, I was able to configure and compile against the Debian 3.1 packages as installed by default:<br />
<br />
<pre><br />
./configure --with-aolserver=/usr<br />
make "EXTRA_INCLUDES=-I/usr/include/tcl8.4 -I/usr/include/aolserver4"<br />
</pre><br />
<br />
== extending PHP to take advantage of AOLServer ==<br />
<br />
http://aolserver.org/docs/devel/c/api/c-ch3.htm#37064<br />
<br />
proposal: write a PHP extension to provide PHP functions to access AOLServer database pools (and perhaps other important features like shared memory).<br />
<br />
In other words, provide PHP functions:<br />
<br />
<pre><br />
ns_db_gethandle<br />
ns_db_select<br />
</pre><br />
<br />
And so on. It should be nearly trivial to do this, and give PHP on AOLServer a very powerful advantage over PHP on Apache.<br />
<br />
[http://www.webtechniques.com/archives/2001/01/junk/ Extending PHP By Sterling Hughes]</div>Cavemanhttps://panoptic.com/mediawiki/aolserver/index.php?title=Talk:How_to_set_up_PHP_under_AOLserver&diff=4576Talk:How to set up PHP under AOLserver2005-12-09T02:11:43Z<p>Caveman: </p>
<hr />
<div>I cannot get php-5.1.1 to build with Debian 3.1 package of aolserver4 and aolserver4-dev (which is built with --prefix=/usr/lib/aolserver4):<br />
<br />
<pre><br />
sam@caveman:~/downloads/php.net/php-5.1.1$ ./configure --with-aolserver=/usr/lib/aolserver4<br />
loading cache ./config.cache<br />
...<br />
...<br />
<br />
Configuring SAPI modules<br />
checking for AOLserver support... /usr/lib/aolserver4<br />
configure: error: Please specify the path to the source distribution of AOLserver using --with-aolserver-src=DIR<br />
sam@caveman:~/downloads/php.net/php-5.1.1$<br />
</pre><br />
<br />
* ''I only ever tested this against PHP 4.3.7 -- I don't know what is required to make it work with PHP 5.1.1. If you figure it out, please update the page. -- [[User:Dossy|Dossy]] 12:05, 7 December 2005 (EST)''<br />
<br />
** I opened a PHP bug issue for this: [http://bugs.php.net/bug.php?id=35605] --[[User:Caveman|Caveman]] 14:05, 8 December 2005 (EST)<br />
<br />
*** This may be an issue more with the way Debian 3.1 installs AOLServer 4 than anything else. The "proper" PHP configure command should be:<br />
<pre><br />
./configure --with-aolserver=/path/to/installed/aolserver<br />
</pre><br />
<br />
Debian 3.1 configures AOLServer with a prefix of "/usr/lib/aolserver4". However, using this as the "/path/to/installed/aolserver" results in the same error and a request for "--with-aolserver-src".<br />
<br />
**** I configured and installed aolserver4 from source into "/home/sam/aolserver". PHP configure finally completed successfully. However, PHP compile still failed:<br />
<br />
<pre><br />
/bin/sh /home/sam/downloads/php.net/php-5.1.1/libtool --silent --preserve-dup-deps --mode=compile /home/sam/downloads/php.net/php-5.1.1/meta_ccld -Isapi/aolserver/ -I/home/sam/downloads/php.net/php-5.1.1/sapi/aolserver/ -DPHP_ATOM_INC -I/home/sam/downloads/php.net/php-5.1.1/include -I/home/sam/downloads/php.net/php-5.1.1/main -I/home/sam/downloads/php.net/php-5.1.1 -I/home/sam/aolserver/include -I/usr/include/libxml2 -I/home/sam/downloads/php.net/php-5.1.1/ext/date/lib -I/home/sam/downloads/php.net/php-5.1.1/TSRM -I/home/sam/downloads/php.net/php-5.1.1/Zend -D_REENTRANT -g -O2 -pthread -DZTS -prefer-non-pic -c /home/sam/downloads/php.net/php-5.1.1/sapi/aolserver/aolserver.c -o sapi/aolserver/aolserver.lo<br />
In file included from /home/sam/aolserver/include/ns.h:62,<br />
from /home/sam/downloads/php.net/php-5.1.1/sapi/aolserver/aolserver.c:49:<br />
/home/sam/aolserver/include/nsthread.h:125:17: tcl.h: No such file or directory<br />
</pre><br />
<br />
This was obviously an error finding "tcl.h". I manually edited the PHP "Makefile" and set:<br />
<pre><br />
EXTRA_INCLUDES = -I/usr/include/tcl8.4<br />
</pre><br />
<br />
This allowed PHP compilation to complete. The module loaded successfully and PHP scripts work as expected (see [http://caveman.org/phpinfo/ phpinfo output]). --[[User:Caveman|Caveman]] 19:05, 8 December 2005 (EST)<br />
<br />
----<br />
<br />
With trial and error, I was able to configure and compile against the Debian 3.1 packages as installed by default:<br />
<br />
<pre><br />
./configure --with-aolserver=/usr<br />
make "EXTRA_INCLUDES=-I/usr/include/tcl8.4 -I/usr/include/aolserver4"<br />
</pre><br />
<br />
== extending PHP to take advantage of AOLServer ==<br />
<br />
http://aolserver.org/docs/devel/c/api/c-ch3.htm#37064<br />
<br />
proposal: write a PHP extension to provide PHP functions to access AOLServer database pools (and perhaps other important features like shared memory).<br />
<br />
In other words, provide PHP functions:<br />
<br />
<pre><br />
ns_db_gethandle<br />
ns_db_select<br />
</pre><br />
<br />
And so on. It should be nearly trivial to do this, and give PHP on AOLServer a very powerful advantage over PHP on Apache.</div>Cavemanhttps://panoptic.com/mediawiki/aolserver/index.php?title=Talk:How_to_set_up_PHP_under_AOLserver&diff=4575Talk:How to set up PHP under AOLserver2005-12-09T02:05:25Z<p>Caveman: </p>
<hr />
<div>I've downloaded the aolserver src both directly and via the Debian source package, but cannot get php-5.1.1 to build:<br />
<br />
<pre><br />
sam@caveman:~/downloads/php.net/php-5.1.1$ ./configure --with-aolserver --with-aolserver-src=/home/sam/downloads/aolserver.org/aolserver-4.0.10<br />
aolserver-4.0.10 aolserver-4.0.10-src.tar.gz<br />
sam@caveman:~/downloads/php.net/php-5.1.1$ ./configure --with-aolserver --with-aolserver-src=/home/sam/downloads/aolserver.org/aolserver-4.0.10 --enable-shared<br />
loading cache ./config.cache<br />
checking for Cygwin environment... no<br />
checking for mingw32 environment... no<br />
checking for egrep... grep -E<br />
checking for a sed that does not truncate output... /bin/sed<br />
checking host system type... i686-pc-linux-gnu<br />
checking target system type... i686-pc-linux-gnu<br />
checking for gcc... gcc<br />
checking whether the C compiler (gcc ) works... yes<br />
checking whether the C compiler (gcc ) is a cross-compiler... no<br />
checking whether we are using GNU C... yes<br />
checking whether gcc accepts -g... yes<br />
checking whether gcc and cc understand -c and -o together... yes<br />
checking how to run the C preprocessor... gcc -E<br />
checking for AIX... no<br />
checking whether ln -s works... yes<br />
checking if compiler supports -R... no<br />
checking if compiler supports -Wl,-rpath,... yes<br />
checking for re2c... re2c<br />
checking for re2c version... invalid<br />
configure: warning: You will need re2c 0.98 or later if you want to regenerate PHP parsers.<br />
checking for gawk... gawk<br />
checking for bison... bison -y<br />
checking for bison version... 1.875 (ok)<br />
checking for flex... flex<br />
checking for yywrap in -lfl... yes<br />
checking lex output file root... lex.yy<br />
checking whether yytext is a pointer... yes<br />
checking for working const... yes<br />
checking for flex version... invalid<br />
configure: warning: flex versions supported for regeneration of the Zend/PHP parsers: 2.5.4 (found: 2.5.31).<br />
checking whether to force non-PIC code in shared modules... yes<br />
checking for pthreads_cflags... -pthread<br />
checking for pthreads_lib...<br />
<br />
Configuring SAPI modules<br />
checking for AOLserver support... yes<br />
configure: error: Please specify the path to the source distribution of AOLserver using --with-aolserver-src=DIR<br />
sam@caveman:~/downloads/php.net/php-5.1.1$<br />
</pre><br />
<br />
<pre><br />
sam@caveman:~/downloads/php.net/php-5.1.1$ ls /home/sam/downloads/aolserver.org/aolserver-4.0.10<br />
ChangeLog configure index.html nscgi nsext nssock tcl<br />
Makefile configure.in ini2tcl.tcl nscp nslog nsssl tcl2ini.tcl<br />
README doc install-sh nsd nspd nsthread tests<br />
aclocal.m4 include license.terms nsdb nsperm sample-config.tcl win32<br />
sam@caveman:~/downloads/php.net/php-5.1.1$<br />
</pre><br />
<br />
Perhaps I am simply an idiot (would not be the first time) but something "no longer works".<br />
<br />
* ''I only ever tested this against PHP 4.3.7 -- I don't know what is required to make it work with PHP 5.1.1. If you figure it out, please update the page. -- [[User:Dossy|Dossy]] 12:05, 7 December 2005 (EST)''<br />
<br />
** I opened a PHP bug issue for this: [http://bugs.php.net/bug.php?id=35605] --[[User:Caveman|Caveman]] 14:05, 8 December 2005 (EST)<br />
<br />
*** This may be an issue more with the way Debian 3.1 installs AOLServer 4 than anything else. The "proper" PHP configure command should be:<br />
<pre><br />
./configure --with-aolserver=/path/to/installed/aolserver<br />
</pre><br />
<br />
Debian 3.1 configures AOLServer with a prefix of "/usr/lib/aolserver4". However, using this as the "/path/to/installed/aolserver" results in the same error and a request for "--with-aolserver-src".<br />
<br />
**** I configured and installed aolserver4 from source into "/home/sam/aolserver". PHP configure finally completed successfully. However, PHP compile still failed:<br />
<br />
<pre><br />
/bin/sh /home/sam/downloads/php.net/php-5.1.1/libtool --silent --preserve-dup-deps --mode=compile /home/sam/downloads/php.net/php-5.1.1/meta_ccld -Isapi/aolserver/ -I/home/sam/downloads/php.net/php-5.1.1/sapi/aolserver/ -DPHP_ATOM_INC -I/home/sam/downloads/php.net/php-5.1.1/include -I/home/sam/downloads/php.net/php-5.1.1/main -I/home/sam/downloads/php.net/php-5.1.1 -I/home/sam/aolserver/include -I/usr/include/libxml2 -I/home/sam/downloads/php.net/php-5.1.1/ext/date/lib -I/home/sam/downloads/php.net/php-5.1.1/TSRM -I/home/sam/downloads/php.net/php-5.1.1/Zend -D_REENTRANT -g -O2 -pthread -DZTS -prefer-non-pic -c /home/sam/downloads/php.net/php-5.1.1/sapi/aolserver/aolserver.c -o sapi/aolserver/aolserver.lo<br />
In file included from /home/sam/aolserver/include/ns.h:62,<br />
from /home/sam/downloads/php.net/php-5.1.1/sapi/aolserver/aolserver.c:49:<br />
/home/sam/aolserver/include/nsthread.h:125:17: tcl.h: No such file or directory<br />
</pre><br />
<br />
This was obviously an error finding "tcl.h". I manually edited the PHP "Makefile" and set:<br />
<pre><br />
EXTRA_INCLUDES = -I/usr/include/tcl8.4<br />
</pre><br />
<br />
This allowed PHP compilation to complete. The module loaded successfully and PHP scripts work as expected (see [http://caveman.org/phpinfo/ phpinfo output]). --[[User:Caveman|Caveman]] 19:05, 8 December 2005 (EST)<br />
<br />
----<br />
<br />
With trial and error, I was able to configure and compile against the Debian 3.1 packages as installed by default:<br />
<br />
<pre><br />
./configure --with-aolserver=/usr<br />
make "EXTRA_INCLUDES=-I/usr/include/tcl8.4 -I/usr/include/aolserver4"<br />
</pre><br />
<br />
== extending PHP to take advantage of AOLServer ==<br />
<br />
http://aolserver.org/docs/devel/c/api/c-ch3.htm#37064<br />
<br />
proposal: write a PHP extension to provide PHP functions to access AOLServer database pools (and perhaps other important features like shared memory).<br />
<br />
In other words, provide PHP functions:<br />
<br />
<pre><br />
ns_db_gethandle<br />
ns_db_select<br />
</pre><br />
<br />
And so on. It should be nearly trivial to do this, and give PHP on AOLServer a very powerful advantage over PHP on Apache.</div>Cavemanhttps://panoptic.com/mediawiki/aolserver/index.php?title=Talk:How_to_set_up_PHP_under_AOLserver&diff=4574Talk:How to set up PHP under AOLserver2005-12-09T02:04:37Z<p>Caveman: </p>
<hr />
<div>I've downloaded the aolserver src both directly and via the Debian source package, but cannot get php-5.1.1 to build:<br />
<br />
<pre><br />
sam@caveman:~/downloads/php.net/php-5.1.1$ ./configure --with-aolserver --with-aolserver-src=/home/sam/downloads/aolserver.org/aolserver-4.0.10<br />
aolserver-4.0.10 aolserver-4.0.10-src.tar.gz<br />
sam@caveman:~/downloads/php.net/php-5.1.1$ ./configure --with-aolserver --with-aolserver-src=/home/sam/downloads/aolserver.org/aolserver-4.0.10 --enable-shared<br />
loading cache ./config.cache<br />
checking for Cygwin environment... no<br />
checking for mingw32 environment... no<br />
checking for egrep... grep -E<br />
checking for a sed that does not truncate output... /bin/sed<br />
checking host system type... i686-pc-linux-gnu<br />
checking target system type... i686-pc-linux-gnu<br />
checking for gcc... gcc<br />
checking whether the C compiler (gcc ) works... yes<br />
checking whether the C compiler (gcc ) is a cross-compiler... no<br />
checking whether we are using GNU C... yes<br />
checking whether gcc accepts -g... yes<br />
checking whether gcc and cc understand -c and -o together... yes<br />
checking how to run the C preprocessor... gcc -E<br />
checking for AIX... no<br />
checking whether ln -s works... yes<br />
checking if compiler supports -R... no<br />
checking if compiler supports -Wl,-rpath,... yes<br />
checking for re2c... re2c<br />
checking for re2c version... invalid<br />
configure: warning: You will need re2c 0.98 or later if you want to regenerate PHP parsers.<br />
checking for gawk... gawk<br />
checking for bison... bison -y<br />
checking for bison version... 1.875 (ok)<br />
checking for flex... flex<br />
checking for yywrap in -lfl... yes<br />
checking lex output file root... lex.yy<br />
checking whether yytext is a pointer... yes<br />
checking for working const... yes<br />
checking for flex version... invalid<br />
configure: warning: flex versions supported for regeneration of the Zend/PHP parsers: 2.5.4 (found: 2.5.31).<br />
checking whether to force non-PIC code in shared modules... yes<br />
checking for pthreads_cflags... -pthread<br />
checking for pthreads_lib...<br />
<br />
Configuring SAPI modules<br />
checking for AOLserver support... yes<br />
configure: error: Please specify the path to the source distribution of AOLserver using --with-aolserver-src=DIR<br />
sam@caveman:~/downloads/php.net/php-5.1.1$<br />
</pre><br />
<br />
<pre><br />
sam@caveman:~/downloads/php.net/php-5.1.1$ ls /home/sam/downloads/aolserver.org/aolserver-4.0.10<br />
ChangeLog configure index.html nscgi nsext nssock tcl<br />
Makefile configure.in ini2tcl.tcl nscp nslog nsssl tcl2ini.tcl<br />
README doc install-sh nsd nspd nsthread tests<br />
aclocal.m4 include license.terms nsdb nsperm sample-config.tcl win32<br />
sam@caveman:~/downloads/php.net/php-5.1.1$<br />
</pre><br />
<br />
Perhaps I am simply an idiot (would not be the first time) but something "no longer works".<br />
<br />
* ''I only ever tested this against PHP 4.3.7 -- I don't know what is required to make it work with PHP 5.1.1. If you figure it out, please update the page. -- [[User:Dossy|Dossy]] 12:05, 7 December 2005 (EST)''<br />
<br />
** I opened a PHP bug issue for this: [http://bugs.php.net/bug.php?id=35605] --[[User:Caveman|Caveman]] 14:05, 8 December 2005 (EST)<br />
<br />
*** This may be an issue more with the way Debian 3.1 installs AOLServer 4 than anything else. The "proper" PHP configure command should be:<br />
<pre><br />
./configure --with-aolserver=/path/to/installed/aolserver<br />
</pre><br />
<br />
Debian 3.1 configures AOLServer with a prefix of "/usr/lib/aolserver4". However, using this as the "/path/to/installed/aolserver" results in the same error and a request for "--with-aolserver-src".<br />
<br />
**** I configured and installed aolserver4 from source into "/home/sam/aolserver". PHP configure finally completed successfully. However, PHP compile still failed:<br />
<br />
<pre><br />
/bin/sh /home/sam/downloads/php.net/php-5.1.1/libtool --silent --preserve-dup-deps --mode=compile /home/sam/downloads/php.net/php-5.1.1/meta_ccld -Isapi/aolserver/ -I/home/sam/downloads/php.net/php-5.1.1/sapi/aolserver/ -DPHP_ATOM_INC -I/home/sam/downloads/php.net/php-5.1.1/include -I/home/sam/downloads/php.net/php-5.1.1/main -I/home/sam/downloads/php.net/php-5.1.1 -I/home/sam/aolserver/include -I/usr/include/libxml2 -I/home/sam/downloads/php.net/php-5.1.1/ext/date/lib -I/home/sam/downloads/php.net/php-5.1.1/TSRM -I/home/sam/downloads/php.net/php-5.1.1/Zend -D_REENTRANT -g -O2 -pthread -DZTS -prefer-non-pic -c /home/sam/downloads/php.net/php-5.1.1/sapi/aolserver/aolserver.c -o sapi/aolserver/aolserver.lo<br />
In file included from /home/sam/aolserver/include/ns.h:62,<br />
from /home/sam/downloads/php.net/php-5.1.1/sapi/aolserver/aolserver.c:49:<br />
/home/sam/aolserver/include/nsthread.h:125:17: tcl.h: No such file or directory<br />
In file included from /home/sam/aolserver/include/ns.h:62,<br />
from /home/sam/downloads/php.net/php-5.1.1/sapi/aolserver/aolserver.c:49:<br />
/home/sam/aolserver/include/nsthread.h:178: error: syntax error before '*' token<br />
/home/sam/aolserver/include/nsthread.h:215: error: syntax error before '*' token<br />
/home/sam/aolserver/include/nsthread.h:294: error: syntax error before '*' token<br />
In file included from /home/sam/downloads/php.net/php-5.1.1/sapi/aolserver/aolserver.c:49:<br />
/home/sam/aolserver/include/ns.h:275: error: syntax error before '*' token<br />
/home/sam/aolserver/include/ns.h:276: error: syntax error before '*' token<br />
/home/sam/aolserver/include/ns.h:277: error: syntax error before '*' token<br />
/home/sam/aolserver/include/ns.h:284: error: syntax error before '*' token<br />
/home/sam/aolserver/include/ns.h:287: error: syntax error before '*' token<br />
/home/sam/aolserver/include/ns.h:442: error: syntax error before '*' token<br />
/home/sam/aolserver/include/ns.h:446: error: syntax error before '*' token<br />
/home/sam/aolserver/include/ns.h:455: error: syntax error before "Ns_CacheSearch"<br />
/home/sam/aolserver/include/ns.h:455: warning: data definition has no type or storage class<br />
/home/sam/aolserver/include/ns.h:507: error: syntax error before "Ns_CacheSearch"<br />
/home/sam/aolserver/include/ns.h:508: error: syntax error before '*' token<br />
/home/sam/aolserver/include/ns.h:545: error: syntax error before "Tcl_DString"<br />
/home/sam/aolserver/include/ns.h:546: error: syntax error before "Tcl_DString"<br />
/home/sam/aolserver/include/ns.h:571: error: syntax error before "Tcl_DString"<br />
/home/sam/aolserver/include/ns.h:575: error: syntax error before "Tcl_DString"<br />
/home/sam/aolserver/include/ns.h:576: error: syntax error before "Tcl_Channel"<br />
/home/sam/aolserver/include/ns.h:580: error: syntax error before "Tcl_DString"<br />
/home/sam/aolserver/include/ns.h:581: error: syntax error before "Tcl_Channel"<br />
/home/sam/aolserver/include/ns.h:585: error: syntax error before "Tcl_Encoding"<br />
/home/sam/aolserver/include/ns.h:586: error: syntax error before "Ns_ConnGetEncoding"<br />
/home/sam/aolserver/include/ns.h:586: warning: data definition has no type or storage class<br />
/home/sam/aolserver/include/ns.h:587: error: syntax error before "Tcl_Encoding"<br />
/home/sam/aolserver/include/ns.h:588: error: syntax error before "Ns_ConnGetUrlEncoding"<br />
/home/sam/aolserver/include/ns.h:588: warning: data definition has no type or storage class<br />
/home/sam/aolserver/include/ns.h:617: error: syntax error before "Tcl_Encoding"<br />
/home/sam/aolserver/include/ns.h:629: error: syntax error before '*' token<br />
/home/sam/aolserver/include/ns.h:630: error: syntax error before '*' token<br />
/home/sam/aolserver/include/ns.h:631: error: syntax error before '*' token<br />
/home/sam/aolserver/include/ns.h:643: error: syntax error before '*' token<br />
/home/sam/aolserver/include/ns.h:644: error: syntax error before '*' token<br />
/home/sam/aolserver/include/ns.h:645: error: syntax error before '*' token<br />
/home/sam/aolserver/include/ns.h:646: error: syntax error before '*' token<br />
/home/sam/aolserver/include/ns.h:647: error: syntax error before '*' token<br />
/home/sam/aolserver/include/ns.h:648: error: syntax error before '*' token<br />
/home/sam/aolserver/include/ns.h:649: error: syntax error before '*' token<br />
/home/sam/aolserver/include/ns.h:649: warning: data definition has no type or storage class<br />
/home/sam/aolserver/include/ns.h:650: error: syntax error before '*' token<br />
/home/sam/aolserver/include/ns.h:672: error: syntax error before '*' token<br />
/home/sam/aolserver/include/ns.h:764: error: syntax error before '*' token<br />
/home/sam/aolserver/include/ns.h:765: error: syntax error before '*' token<br />
/home/sam/aolserver/include/ns.h:771: error: syntax error before '*' token<br />
/home/sam/aolserver/include/ns.h:772: error: syntax error before '*' token<br />
/home/sam/aolserver/include/ns.h:778: error: syntax error before '*' token<br />
/home/sam/aolserver/include/ns.h:780: error: syntax error before '*' token<br />
/home/sam/aolserver/include/ns.h:782: error: syntax error before '*' token<br />
/home/sam/aolserver/include/ns.h:784: error: syntax error before '*' token<br />
/home/sam/aolserver/include/ns.h:850: error: syntax error before "Ns_GetEncoding"<br />
/home/sam/aolserver/include/ns.h:850: warning: data definition has no type or storage class<br />
/home/sam/aolserver/include/ns.h:851: error: syntax error before "Ns_GetFileEncoding"<br />
/home/sam/aolserver/include/ns.h:851: warning: data definition has no type or storage class<br />
/home/sam/aolserver/include/ns.h:852: error: syntax error before "Ns_GetTypeEncoding"<br />
/home/sam/aolserver/include/ns.h:852: warning: data definition has no type or storage class<br />
/home/sam/aolserver/include/ns.h:853: error: syntax error before "Ns_GetCharsetEncoding"<br />
/home/sam/aolserver/include/ns.h:853: warning: data definition has no type or storage class<br />
/home/sam/aolserver/include/ns.h:892: error: syntax error before '*' token<br />
/home/sam/aolserver/include/ns.h:893: error: syntax error before '*' token<br />
/home/sam/aolserver/include/ns.h:894: error: syntax error before '*' token<br />
/home/sam/aolserver/include/ns.h:895: error: syntax error before '*' token<br />
/home/sam/aolserver/include/ns.h:896: error: syntax error before '*' token<br />
/home/sam/aolserver/include/ns.h:904: error: syntax error before '*' token<br />
/home/sam/aolserver/include/ns.h:916: error: syntax error before '*' token<br />
/home/sam/aolserver/include/ns.h:932: error: syntax error before "Tcl_DString"<br />
/home/sam/aolserver/include/ns.h:966: error: syntax error before "Tcl_Channel"<br />
/home/sam/aolserver/include/ns.h:1095: error: syntax error before '*' token<br />
/home/sam/aolserver/include/ns.h:1102: error: syntax error before '*' token<br />
/home/sam/aolserver/include/ns.h:1104: error: syntax error before '*' token<br />
/home/sam/aolserver/include/ns.h:1111: error: syntax error before '*' token<br />
/home/sam/aolserver/include/ns.h:1112: error: syntax error before '*' token<br />
/home/sam/aolserver/include/ns.h:1115: error: syntax error before '*' token<br />
/home/sam/aolserver/include/ns.h:1116: error: syntax error before '*' token<br />
/home/sam/aolserver/include/ns.h:1117: error: syntax error before '*' token<br />
/home/sam/aolserver/include/ns.h:1117: warning: data definition has no type or storage class<br />
/home/sam/aolserver/include/ns.h:1118: error: syntax error before '*' token<br />
/home/sam/aolserver/include/ns.h:1119: error: syntax error before '*' token<br />
/home/sam/aolserver/include/ns.h:1119: warning: data definition has no type or storage class<br />
/home/sam/aolserver/include/ns.h:1120: error: syntax error before '*' token<br />
/home/sam/aolserver/include/ns.h:1122: error: syntax error before '*' token<br />
/home/sam/aolserver/include/ns.h:1123: error: syntax error before '*' token<br />
/home/sam/aolserver/include/ns.h:1133: error: syntax error before '*' token<br />
/home/sam/aolserver/include/ns.h:1134: error: syntax error before '*' token<br />
/home/sam/aolserver/include/ns.h:1135: error: syntax error before '*' token<br />
/home/sam/aolserver/include/ns.h:1136: error: syntax error before '*' token<br />
/home/sam/aolserver/include/ns.h:1136: warning: data definition has no type or storage class<br />
/home/sam/aolserver/include/ns.h:1143: error: syntax error before '*' token<br />
/home/sam/aolserver/include/ns.h:1144: error: syntax error before '*' token<br />
/home/sam/aolserver/include/ns.h:1145: error: syntax error before '*' token<br />
/home/sam/aolserver/include/ns.h:1146: error: syntax error before '*' token<br />
/home/sam/aolserver/include/ns.h:1152: error: syntax error before '*' token<br />
/home/sam/aolserver/include/ns.h:1162: error: syntax error before '*' token<br />
/home/sam/aolserver/include/ns.h:1168: error: syntax error before '*' token<br />
/home/sam/aolserver/include/ns.h:1170: error: syntax error before '*' token<br />
/home/sam/aolserver/include/ns.h:1172: error: syntax error before '*' token<br />
/home/sam/aolserver/include/ns.h:1174: error: syntax error before '*' token<br />
/home/sam/aolserver/include/ns.h:1181: error: syntax error before '*' token<br />
/home/sam/aolserver/include/ns.h:1182: error: syntax error before '*' token<br />
/home/sam/aolserver/include/ns.h:1221: error: syntax error before '*' token<br />
/home/sam/downloads/php.net/php-5.1.1/sapi/aolserver/aolserver.c: In function `php_ns_request_ctor':<br />
/home/sam/downloads/php.net/php-5.1.1/sapi/aolserver/aolserver.c:428: error: `Tcl_DString' undeclared (first use in this function)<br />
/home/sam/downloads/php.net/php-5.1.1/sapi/aolserver/aolserver.c:428: error: (Each undeclared identifier is reported only once<br />
/home/sam/downloads/php.net/php-5.1.1/sapi/aolserver/aolserver.c:428: error: for each function it appears in.)<br />
/home/sam/downloads/php.net/php-5.1.1/sapi/aolserver/aolserver.c:428: error: syntax error before "ds"<br />
/home/sam/downloads/php.net/php-5.1.1/sapi/aolserver/aolserver.c:438: error: `ds' undeclared (first use in this function)<br />
/home/sam/downloads/php.net/php-5.1.1/sapi/aolserver/aolserver.c:442: warning: passing arg 1 of `strlen' makes pointer from integer without a cast<br />
/home/sam/downloads/php.net/php-5.1.1/sapi/aolserver/aolserver.c:442: warning: passing arg 2 of `memcpy' makes pointer from integer without a cast<br />
/home/sam/downloads/php.net/php-5.1.1/sapi/aolserver/aolserver.c:442: warning: passing arg 1 of `__strdup' makes pointer from integer without a cast<br />
make: *** [sapi/aolserver/aolserver.lo] Error 1<br />
</pre><br />
<br />
This was obviously an error finding "tcl.h". I manually edited the PHP "Makefile" and set:<br />
<pre><br />
EXTRA_INCLUDES = -I/usr/include/tcl8.4<br />
</pre><br />
<br />
This allowed PHP compilation to complete. The module loaded successfully and PHP scripts work as expected (see [http://caveman.org/phpinfo/ phpinfo output]). --[[User:Caveman|Caveman]] 19:05, 8 December 2005 (EST)<br />
<br />
----<br />
<br />
With trial and error, I was able to configure and compile against the Debian 3.1 packages as installed by default:<br />
<br />
<pre><br />
./configure --with-aolserver=/usr<br />
make "EXTRA_INCLUDES=-I/usr/include/tcl8.4 -I/usr/include/aolserver4"<br />
</pre><br />
<br />
== extending PHP to take advantage of AOLServer ==<br />
<br />
http://aolserver.org/docs/devel/c/api/c-ch3.htm#37064<br />
<br />
proposal: write a PHP extension to provide PHP functions to access AOLServer database pools (and perhaps other important features like shared memory).<br />
<br />
In other words, provide PHP functions:<br />
<br />
<pre><br />
ns_db_gethandle<br />
ns_db_select<br />
</pre><br />
<br />
And so on. It should be nearly trivial to do this, and give PHP on AOLServer a very powerful advantage over PHP on Apache.</div>Cavemanhttps://panoptic.com/mediawiki/aolserver/index.php?title=Talk:How_to_set_up_PHP_under_AOLserver&diff=4573Talk:How to set up PHP under AOLserver2005-12-09T00:09:35Z<p>Caveman: /* link to phpinfo output */</p>
<hr />
<div>I've downloaded the aolserver src both directly and via the Debian source package, but cannot get php-5.1.1 to build:<br />
<br />
<pre><br />
sam@caveman:~/downloads/php.net/php-5.1.1$ ./configure --with-aolserver --with-aolserver-src=/home/sam/downloads/aolserver.org/aolserver-4.0.10<br />
aolserver-4.0.10 aolserver-4.0.10-src.tar.gz<br />
sam@caveman:~/downloads/php.net/php-5.1.1$ ./configure --with-aolserver --with-aolserver-src=/home/sam/downloads/aolserver.org/aolserver-4.0.10 --enable-shared<br />
loading cache ./config.cache<br />
checking for Cygwin environment... no<br />
checking for mingw32 environment... no<br />
checking for egrep... grep -E<br />
checking for a sed that does not truncate output... /bin/sed<br />
checking host system type... i686-pc-linux-gnu<br />
checking target system type... i686-pc-linux-gnu<br />
checking for gcc... gcc<br />
checking whether the C compiler (gcc ) works... yes<br />
checking whether the C compiler (gcc ) is a cross-compiler... no<br />
checking whether we are using GNU C... yes<br />
checking whether gcc accepts -g... yes<br />
checking whether gcc and cc understand -c and -o together... yes<br />
checking how to run the C preprocessor... gcc -E<br />
checking for AIX... no<br />
checking whether ln -s works... yes<br />
checking if compiler supports -R... no<br />
checking if compiler supports -Wl,-rpath,... yes<br />
checking for re2c... re2c<br />
checking for re2c version... invalid<br />
configure: warning: You will need re2c 0.98 or later if you want to regenerate PHP parsers.<br />
checking for gawk... gawk<br />
checking for bison... bison -y<br />
checking for bison version... 1.875 (ok)<br />
checking for flex... flex<br />
checking for yywrap in -lfl... yes<br />
checking lex output file root... lex.yy<br />
checking whether yytext is a pointer... yes<br />
checking for working const... yes<br />
checking for flex version... invalid<br />
configure: warning: flex versions supported for regeneration of the Zend/PHP parsers: 2.5.4 (found: 2.5.31).<br />
checking whether to force non-PIC code in shared modules... yes<br />
checking for pthreads_cflags... -pthread<br />
checking for pthreads_lib...<br />
<br />
Configuring SAPI modules<br />
checking for AOLserver support... yes<br />
configure: error: Please specify the path to the source distribution of AOLserver using --with-aolserver-src=DIR<br />
sam@caveman:~/downloads/php.net/php-5.1.1$<br />
</pre><br />
<br />
<pre><br />
sam@caveman:~/downloads/php.net/php-5.1.1$ ls /home/sam/downloads/aolserver.org/aolserver-4.0.10<br />
ChangeLog configure index.html nscgi nsext nssock tcl<br />
Makefile configure.in ini2tcl.tcl nscp nslog nsssl tcl2ini.tcl<br />
README doc install-sh nsd nspd nsthread tests<br />
aclocal.m4 include license.terms nsdb nsperm sample-config.tcl win32<br />
sam@caveman:~/downloads/php.net/php-5.1.1$<br />
</pre><br />
<br />
Perhaps I am simply an idiot (would not be the first time) but something "no longer works".<br />
<br />
* ''I only ever tested this against PHP 4.3.7 -- I don't know what is required to make it work with PHP 5.1.1. If you figure it out, please update the page. -- [[User:Dossy|Dossy]] 12:05, 7 December 2005 (EST)''<br />
<br />
** I opened a PHP bug issue for this: [http://bugs.php.net/bug.php?id=35605] --[[User:Caveman|Caveman]] 14:05, 8 December 2005 (EST)<br />
<br />
*** This may be an issue more with the way Debian 3.1 installs AOLServer 4 than anything else. The "proper" PHP configure command should be:<br />
<pre><br />
./configure --with-aolserver=/path/to/installed/aolserver<br />
</pre><br />
<br />
Debian 3.1 configures AOLServer with a prefix of "/usr/lib/aolserver4". However, using this as the "/path/to/installed/aolserver" results in the same error and a request for "--with-aolserver-src".<br />
<br />
**** I configured and installed aolserver4 from source into "/home/sam/aolserver". PHP configure finally completed successfully. However, PHP compile still failed:<br />
<br />
<pre><br />
/bin/sh /home/sam/downloads/php.net/php-5.1.1/libtool --silent --preserve-dup-deps --mode=compile /home/sam/downloads/php.net/php-5.1.1/meta_ccld -Isapi/aolserver/ -I/home/sam/downloads/php.net/php-5.1.1/sapi/aolserver/ -DPHP_ATOM_INC -I/home/sam/downloads/php.net/php-5.1.1/include -I/home/sam/downloads/php.net/php-5.1.1/main -I/home/sam/downloads/php.net/php-5.1.1 -I/home/sam/aolserver/include -I/usr/include/libxml2 -I/home/sam/downloads/php.net/php-5.1.1/ext/date/lib -I/home/sam/downloads/php.net/php-5.1.1/TSRM -I/home/sam/downloads/php.net/php-5.1.1/Zend -D_REENTRANT -g -O2 -pthread -DZTS -prefer-non-pic -c /home/sam/downloads/php.net/php-5.1.1/sapi/aolserver/aolserver.c -o sapi/aolserver/aolserver.lo<br />
In file included from /home/sam/aolserver/include/ns.h:62,<br />
from /home/sam/downloads/php.net/php-5.1.1/sapi/aolserver/aolserver.c:49:<br />
/home/sam/aolserver/include/nsthread.h:125:17: tcl.h: No such file or directory<br />
In file included from /home/sam/aolserver/include/ns.h:62,<br />
from /home/sam/downloads/php.net/php-5.1.1/sapi/aolserver/aolserver.c:49:<br />
/home/sam/aolserver/include/nsthread.h:178: error: syntax error before '*' token<br />
/home/sam/aolserver/include/nsthread.h:215: error: syntax error before '*' token<br />
/home/sam/aolserver/include/nsthread.h:294: error: syntax error before '*' token<br />
In file included from /home/sam/downloads/php.net/php-5.1.1/sapi/aolserver/aolserver.c:49:<br />
/home/sam/aolserver/include/ns.h:275: error: syntax error before '*' token<br />
/home/sam/aolserver/include/ns.h:276: error: syntax error before '*' token<br />
/home/sam/aolserver/include/ns.h:277: error: syntax error before '*' token<br />
/home/sam/aolserver/include/ns.h:284: error: syntax error before '*' token<br />
/home/sam/aolserver/include/ns.h:287: error: syntax error before '*' token<br />
/home/sam/aolserver/include/ns.h:442: error: syntax error before '*' token<br />
/home/sam/aolserver/include/ns.h:446: error: syntax error before '*' token<br />
/home/sam/aolserver/include/ns.h:455: error: syntax error before "Ns_CacheSearch"<br />
/home/sam/aolserver/include/ns.h:455: warning: data definition has no type or storage class<br />
/home/sam/aolserver/include/ns.h:507: error: syntax error before "Ns_CacheSearch"<br />
/home/sam/aolserver/include/ns.h:508: error: syntax error before '*' token<br />
/home/sam/aolserver/include/ns.h:545: error: syntax error before "Tcl_DString"<br />
/home/sam/aolserver/include/ns.h:546: error: syntax error before "Tcl_DString"<br />
/home/sam/aolserver/include/ns.h:571: error: syntax error before "Tcl_DString"<br />
/home/sam/aolserver/include/ns.h:575: error: syntax error before "Tcl_DString"<br />
/home/sam/aolserver/include/ns.h:576: error: syntax error before "Tcl_Channel"<br />
/home/sam/aolserver/include/ns.h:580: error: syntax error before "Tcl_DString"<br />
/home/sam/aolserver/include/ns.h:581: error: syntax error before "Tcl_Channel"<br />
/home/sam/aolserver/include/ns.h:585: error: syntax error before "Tcl_Encoding"<br />
/home/sam/aolserver/include/ns.h:586: error: syntax error before "Ns_ConnGetEncoding"<br />
/home/sam/aolserver/include/ns.h:586: warning: data definition has no type or storage class<br />
/home/sam/aolserver/include/ns.h:587: error: syntax error before "Tcl_Encoding"<br />
/home/sam/aolserver/include/ns.h:588: error: syntax error before "Ns_ConnGetUrlEncoding"<br />
/home/sam/aolserver/include/ns.h:588: warning: data definition has no type or storage class<br />
/home/sam/aolserver/include/ns.h:617: error: syntax error before "Tcl_Encoding"<br />
/home/sam/aolserver/include/ns.h:629: error: syntax error before '*' token<br />
/home/sam/aolserver/include/ns.h:630: error: syntax error before '*' token<br />
/home/sam/aolserver/include/ns.h:631: error: syntax error before '*' token<br />
/home/sam/aolserver/include/ns.h:643: error: syntax error before '*' token<br />
/home/sam/aolserver/include/ns.h:644: error: syntax error before '*' token<br />
/home/sam/aolserver/include/ns.h:645: error: syntax error before '*' token<br />
/home/sam/aolserver/include/ns.h:646: error: syntax error before '*' token<br />
/home/sam/aolserver/include/ns.h:647: error: syntax error before '*' token<br />
/home/sam/aolserver/include/ns.h:648: error: syntax error before '*' token<br />
/home/sam/aolserver/include/ns.h:649: error: syntax error before '*' token<br />
/home/sam/aolserver/include/ns.h:649: warning: data definition has no type or storage class<br />
/home/sam/aolserver/include/ns.h:650: error: syntax error before '*' token<br />
/home/sam/aolserver/include/ns.h:672: error: syntax error before '*' token<br />
/home/sam/aolserver/include/ns.h:764: error: syntax error before '*' token<br />
/home/sam/aolserver/include/ns.h:765: error: syntax error before '*' token<br />
/home/sam/aolserver/include/ns.h:771: error: syntax error before '*' token<br />
/home/sam/aolserver/include/ns.h:772: error: syntax error before '*' token<br />
/home/sam/aolserver/include/ns.h:778: error: syntax error before '*' token<br />
/home/sam/aolserver/include/ns.h:780: error: syntax error before '*' token<br />
/home/sam/aolserver/include/ns.h:782: error: syntax error before '*' token<br />
/home/sam/aolserver/include/ns.h:784: error: syntax error before '*' token<br />
/home/sam/aolserver/include/ns.h:850: error: syntax error before "Ns_GetEncoding"<br />
/home/sam/aolserver/include/ns.h:850: warning: data definition has no type or storage class<br />
/home/sam/aolserver/include/ns.h:851: error: syntax error before "Ns_GetFileEncoding"<br />
/home/sam/aolserver/include/ns.h:851: warning: data definition has no type or storage class<br />
/home/sam/aolserver/include/ns.h:852: error: syntax error before "Ns_GetTypeEncoding"<br />
/home/sam/aolserver/include/ns.h:852: warning: data definition has no type or storage class<br />
/home/sam/aolserver/include/ns.h:853: error: syntax error before "Ns_GetCharsetEncoding"<br />
/home/sam/aolserver/include/ns.h:853: warning: data definition has no type or storage class<br />
/home/sam/aolserver/include/ns.h:892: error: syntax error before '*' token<br />
/home/sam/aolserver/include/ns.h:893: error: syntax error before '*' token<br />
/home/sam/aolserver/include/ns.h:894: error: syntax error before '*' token<br />
/home/sam/aolserver/include/ns.h:895: error: syntax error before '*' token<br />
/home/sam/aolserver/include/ns.h:896: error: syntax error before '*' token<br />
/home/sam/aolserver/include/ns.h:904: error: syntax error before '*' token<br />
/home/sam/aolserver/include/ns.h:916: error: syntax error before '*' token<br />
/home/sam/aolserver/include/ns.h:932: error: syntax error before "Tcl_DString"<br />
/home/sam/aolserver/include/ns.h:966: error: syntax error before "Tcl_Channel"<br />
/home/sam/aolserver/include/ns.h:1095: error: syntax error before '*' token<br />
/home/sam/aolserver/include/ns.h:1102: error: syntax error before '*' token<br />
/home/sam/aolserver/include/ns.h:1104: error: syntax error before '*' token<br />
/home/sam/aolserver/include/ns.h:1111: error: syntax error before '*' token<br />
/home/sam/aolserver/include/ns.h:1112: error: syntax error before '*' token<br />
/home/sam/aolserver/include/ns.h:1115: error: syntax error before '*' token<br />
/home/sam/aolserver/include/ns.h:1116: error: syntax error before '*' token<br />
/home/sam/aolserver/include/ns.h:1117: error: syntax error before '*' token<br />
/home/sam/aolserver/include/ns.h:1117: warning: data definition has no type or storage class<br />
/home/sam/aolserver/include/ns.h:1118: error: syntax error before '*' token<br />
/home/sam/aolserver/include/ns.h:1119: error: syntax error before '*' token<br />
/home/sam/aolserver/include/ns.h:1119: warning: data definition has no type or storage class<br />
/home/sam/aolserver/include/ns.h:1120: error: syntax error before '*' token<br />
/home/sam/aolserver/include/ns.h:1122: error: syntax error before '*' token<br />
/home/sam/aolserver/include/ns.h:1123: error: syntax error before '*' token<br />
/home/sam/aolserver/include/ns.h:1133: error: syntax error before '*' token<br />
/home/sam/aolserver/include/ns.h:1134: error: syntax error before '*' token<br />
/home/sam/aolserver/include/ns.h:1135: error: syntax error before '*' token<br />
/home/sam/aolserver/include/ns.h:1136: error: syntax error before '*' token<br />
/home/sam/aolserver/include/ns.h:1136: warning: data definition has no type or storage class<br />
/home/sam/aolserver/include/ns.h:1143: error: syntax error before '*' token<br />
/home/sam/aolserver/include/ns.h:1144: error: syntax error before '*' token<br />
/home/sam/aolserver/include/ns.h:1145: error: syntax error before '*' token<br />
/home/sam/aolserver/include/ns.h:1146: error: syntax error before '*' token<br />
/home/sam/aolserver/include/ns.h:1152: error: syntax error before '*' token<br />
/home/sam/aolserver/include/ns.h:1162: error: syntax error before '*' token<br />
/home/sam/aolserver/include/ns.h:1168: error: syntax error before '*' token<br />
/home/sam/aolserver/include/ns.h:1170: error: syntax error before '*' token<br />
/home/sam/aolserver/include/ns.h:1172: error: syntax error before '*' token<br />
/home/sam/aolserver/include/ns.h:1174: error: syntax error before '*' token<br />
/home/sam/aolserver/include/ns.h:1181: error: syntax error before '*' token<br />
/home/sam/aolserver/include/ns.h:1182: error: syntax error before '*' token<br />
/home/sam/aolserver/include/ns.h:1221: error: syntax error before '*' token<br />
/home/sam/downloads/php.net/php-5.1.1/sapi/aolserver/aolserver.c: In function `php_ns_request_ctor':<br />
/home/sam/downloads/php.net/php-5.1.1/sapi/aolserver/aolserver.c:428: error: `Tcl_DString' undeclared (first use in this function)<br />
/home/sam/downloads/php.net/php-5.1.1/sapi/aolserver/aolserver.c:428: error: (Each undeclared identifier is reported only once<br />
/home/sam/downloads/php.net/php-5.1.1/sapi/aolserver/aolserver.c:428: error: for each function it appears in.)<br />
/home/sam/downloads/php.net/php-5.1.1/sapi/aolserver/aolserver.c:428: error: syntax error before "ds"<br />
/home/sam/downloads/php.net/php-5.1.1/sapi/aolserver/aolserver.c:438: error: `ds' undeclared (first use in this function)<br />
/home/sam/downloads/php.net/php-5.1.1/sapi/aolserver/aolserver.c:442: warning: passing arg 1 of `strlen' makes pointer from integer without a cast<br />
/home/sam/downloads/php.net/php-5.1.1/sapi/aolserver/aolserver.c:442: warning: passing arg 2 of `memcpy' makes pointer from integer without a cast<br />
/home/sam/downloads/php.net/php-5.1.1/sapi/aolserver/aolserver.c:442: warning: passing arg 1 of `__strdup' makes pointer from integer without a cast<br />
make: *** [sapi/aolserver/aolserver.lo] Error 1<br />
</pre><br />
<br />
This was obviously an error finding "tcl.h". I manually edited the PHP "Makefile" and set:<br />
<pre><br />
EXTRA_INCLUDES = -I/usr/include/tcl8.4<br />
</pre><br />
<br />
This allowed PHP compilation to complete. The module loaded successfully and PHP scripts work as expected (see [http://caveman.org/phpinfo/ phpinfo output]). --[[User:Caveman|Caveman]] 19:05, 8 December 2005 (EST)<br />
<br />
== extending PHP to take advantage of AOLServer ==<br />
<br />
http://aolserver.org/docs/devel/c/api/c-ch3.htm#37064<br />
<br />
proposal: write a PHP extension to provide PHP functions to access AOLServer database pools (and perhaps other important features like shared memory).<br />
<br />
In other words, provide PHP functions:<br />
<br />
<pre><br />
ns_db_gethandle<br />
ns_db_select<br />
</pre><br />
<br />
And so on. It should be nearly trivial to do this, and give PHP on AOLServer a very powerful advantage over PHP on Apache.</div>Caveman