AOLserver Wiki - User contributions [en]

User:Josephbui

2012-01-23T20:33:22Z

Josephbui:

Joseph Bui used to work as an TCL developer in Washington, DC... unfortunately, the company was purchased by a Java shop. And then that company was purchased by a VB shop. I don't use AOLserver or TCL for work anymore. On the plus side, I guess I'm going to get my personal website running again (using AOLServer of course) in case of layoffs.

== Pages To Delete ==

I try to delete irrelevant pages from the site when I see them.

[[Category:Person|Bui, Joseph]]

User:Josephbui

2012-01-23T20:32:37Z

Josephbui:

Joseph Bui used to work as an TCL developer in Washington, DC... unfortunately, the company was purchased by a Java shop. And then that company was purchased by a VB shop. I don't use AOLserver or TCL for work anymore. On the plus side, I guess I'm going to get back my personal website running again (using AOLServer of course).

== Pages To Delete ==

I try to delete irrelevant pages from the site when I see them.

[[Category:Person|Bui, Joseph]]

User:Josephbui

2011-02-07T20:54:09Z

Josephbui:

Ns writecontent

2011-02-07T20:24:40Z

Josephbui: Reverted edits by Guru (Talk) to last revision by Rcobb

<manpage>ns_writecontent</manpage>

'''NAME'''

: ns_writecontent - write content of request to Tcl channel

'''SYNOPSIS'''

: '''ns_writecontent''' ''?conn?'' ''channel''

'''DESCRIPTION'''

: ns_writecontent is identical to [[ns_conncptofp]]. It reads the content body of the conn (HTTP request) and copies it to the given Tcl I/O channel.

'''EXAMPLES'''

@@COMMAND_EXAMPLES@@

'''SEE ALSO'''

: ns_conncptofp

'''NOTES'''
:* Throws the error "could not copy content (likely client disconnect)" if sufficient (based on content-length) content can not be read.

[[Category:Core Tcl API]]

Dqd utils

2011-02-07T20:24:31Z

Josephbui: Reverted edits by Guru (Talk) to last revision by WikiSysop

By [[Rob Mayoff]].
* dqd_internalredirect - a wrapper around the C API function Ns_ConnRedirect. This lets you send back the contents of a different URL (from the same server) without letting the client know.
* dqd_md5 - computes MD5 hashes (cryptographic checksums).
* dqd_nssetToList - extracts an ns_set's values into a Tcl list.
* unlist - assigns the elements of a Tcl list to individual Tcl variables, efficiently. Yes, I left off the dqd_ prefix on this one.
* dqd_detachfile and dqd_attachfile - share a Tcl channel across requests/threads/interpreters.
* dqd_register_proxy - register a proc to handle proxy requests from browsers

http://dqd.com/~mayoff/aolserver/#dqd_utils

ProjectOpen

2010-04-16T20:46:19Z

Josephbui:

]project-open[ is a Web-based project management system for companies with 2-200 employees in the consulting, engineering, advertising, and translation sectors. ]po[ helps you to run your business by covering the entire project life cycle from sales (CRM-light), staffing, execution (timesheet, controlling, incidents, discussions, and file storage) to invoicing and payment.

The ]po[ architecture is designed for mission-critical applications with a rock-solid infrastructure based on [[AOLserver]] and [[OpenACS]].

== Use of AOLserver ==

There are about 1000 companies today (March 2007) running ]project-open[:

* About half of the companies use AOLServer 4.0.beta10 on Windows
* The other half uses AOLServer 3.3oacs on Linux
* There are a dozen or so installations on Solaris and BSD (Mac OS)

== ]project-open[ Modules ==

* [http://www.project-open.org/product/modules/pm Projects Management]: Project, Subprojects, Project Planning, Resource Planning, Project Tracking, integration with [http://sourceforge.net/projects/ganttproject/ GanttProject], Project Templates, ...

* [http://www.project-open.org/product/modules/finance Project Finance]: Timesheet, Exenses and Travel Costs, Invoicing (fixed & variable cost projects), Project Controlling, Financial Reporting, Profit & Loss, Accounting Export

* [http://www.project-open.org/product/modules/ Project Collaboration]: Wiki, Forum, Filestorage, Bug Tracker, Incident Management

== Links ==

* SourceForge: http://sourceforge.net/projects/project-open/
* Developers: http://www.project-open.org/
* Commercial: http://www.project-open.com/

ProjectOpen

2010-04-16T20:44:52Z

Josephbui: Reverted edits by HarryLeC (Talk) to last revision by Josephbui

]project-open[ is a Web-based project management system for companies with 2-200 employees in the consulting, engineering, advertising, and translation sectors. ]po[ helps you to run your business by covering the entire project life cycle from sales (CRM-light), staffing, execution (timesheet, controlling, incidents, discussions, and file storage) to invoicing and payment.

The ]po[ architecture is designed for mission-critical applications with a rock-solid infrastructure based on [[AOLserver]] and [[OpenACS]].

== Use of AOLserver ==

There are about 1000 companies today (March 2007) running ]project-open[:

* About half of the companies use AOLServer 4.0.beta10 on Windows
* The other half uses AOLServer 3.3oacs on Linux
* There are a dozen or so installations on Solaris and BSD (Mac OS)

== ]project-open[ Modules ==

* [http://www.project-open.org/product/modules/pm Projects Management]: Project, Subprojects, Project Planning, Resource Planning, Project Tracking, integration with [http://sourceforge.net/projects/ganttproject/ GanttProject], Project Templates, ...

* [http://www.project-open.org/product/modules/finance Project Finance]: Timesheet, Exenses and Travel Costs, Invoicing (fixed & variable cost projects), Project Controlling, Financial Reporting, Profit & Loss, Accounting Export

* [http://www.project-open.org/product/modules/ Project Collaboration]: Wiki, Forum, Filestorage, Bug Tracker, Incident Management
* [http://www.mustuniversity.com/Schools-Majors/Business-and-Management-Masters-Degree.html MBA degree]
* [http://www.mustuniversity.com/Programs/Diploma/Graduate-Diploma.html graduate diploma]

== Links ==

* SourceForge: http://sourceforge.net/projects/project-open/
* Developers: http://www.project-open.org/
* Commercial: http://www.project-open.com/

User talk:Josephbui

2010-03-15T16:25:41Z

Josephbui:

Joseph: Thanks for your help cleaning up the wiki vandalism. Would you like Admin privileges to take care of deletes and blocks? -- [[User:Dossy|Dossy]] 14:30, 15 March 2010 (UTC)

Dossy: Sure, thanks! [[User:Josephbui|Josephbui]] 16:25, 15 March 2010 (UTC)

Ns sendmail

2010-03-05T14:34:54Z

Josephbui: Undo revision 5691 by Esper (Talk)

{{manpage|ns_sendmail}}

----

'''NAME'''

: ns_sendmail - Deliver a mail message using SMTP

'''SYNOPSIS'''

: '''ns_sendmail''' ''to from subject body ?extraheaders? ?bcc?''

'''DESCRIPTION'''

: This command delivers a mail message using a simple SMTP client implementation.

: ''to'' and ''bcc'' are strings containing comma-separated lists of email addresses and will be supplied as the "RCPT TO" portion of the SMTP transaction. ''from'' will be used as the "MAIL FROM" portion of the SMTP transaction. By default, the following mail message's headers are constructed by '''ns_sendmail''': To, From, Subject, Date. ''subject'' is used for the Subject header, and the system's current time is used for the Date: header. Additional headers can be supplied using the ''extraheaders'' [[ns_set]], where the key is used as the header name and the value is used as the header value.

: '''Note:''' This implementation of an SMTP client is very primitive, not very flexible, does very little error checking, is not very robust as it does not handle SMTP failures by retrying, etc. A better choice would be to use the [http://tcllib.sourceforge.net/doc/smtp.html Tcllib smtp] package.

'''CONFIGURATION'''

: The SMTP server used for mail delivery is controlled through the server's configuration in the '''ns/parameters''' section. The following parameters are currently recognized:

* '''smtphost''' - the FQDN name or IP address of the server to connect to. Default is "localhost".

* '''mailhost''' - if '''smtphost''' is not defined or is an empty string, then the '''mailhost''' parameter is used.

* '''smtptimeout''' - timeout in seconds when interacting with the SMTP server. Default is 60 seconds.

* '''smtpport''' - TCP port used for connecting to the SMTP server. Default is 25.

'''EXAMPLES'''

# Send a simple message from somebody@aolserver.com to nobody@aolserver.com.

ns_sendmail nobody@aolserver.com somebody@aolserver.com \
"Hello, world." "Hi, how are you?"

'''SEE ALSO'''

: [[ns_param]], [[ns_section]], [[ns_set]], [[ns_sockopen]], [http://tcllib.sourceforge.net/doc/smtp.html Tcllib smtp]

[[Category:Core Tcl API]]

Keylkeys

2010-03-04T18:35:53Z

Josephbui: Undo revision 5686 by Jenika (Talk)

Man page: http://aolserver.com/docs/tcl/keylkeys.html

----

'''NAME'''

: keylkeys - Return the keys for a keyed list

'''SYNOPSIS'''

: '''keylkeys''' ''listvar ?key?''

'''DESCRIPTION'''

: This command returns a list of keys for the keyed list ''listvar''. If ''key'' is specified, the values for that key are returned instead.

: Keyed lists are an extension of Tcl provided by the TclX package. They are an alternative to using [[ns_set]], but we highly recommend using [[ns_set]] instead of keyed lists where possible. The commands provided by AOLserver were taken directly from a 1995 version of the TclX package.

'''EXAMPLES'''

% keylset mylist a 1 {b c} 2

% keylkeys mylist
a {b c}

% keylkeys mylist a
1

'''SEE ALSO'''

: TclX [http://wiki.tcl.tk/TclX], [[keyldel]], [[keylget]], [[keylset]]

----

[[Category Documentation]] - [[Category Core Tcl API]]

AOLserver Wiki

2010-03-04T18:35:48Z

Josephbui: Undo revision 5687 by PatriciaCarr (Talk)

Ns getform

2010-03-03T16:11:57Z

Josephbui: Undo revision 5683 by Adrianjackson21 (Talk)

Man page: http://aolserver.com/docs/tcl/ns_getform.html
----

'''NAME'''

: ns_getform - Return the connection formdata ns_set, copying multipart form data into temp files if necessary.

'''SYNOPSIS'''

: '''ns_getform''' ''?charset?''

'''DESCRIPTION'''

: This is a Tcl wrapper to '''[[ns_conn]] form''' that first calls [[ns_urlcharset]] if ''charset'' is specified. In addition, if the request contains multipart form submission, it copies each uploaded file content into a temp file and sets up data to allow access to these temp files using [[ns_getformfile]]. Otherwise, it generally behaves the same as ns_conn form, so see its documentation for more details.

: Use this for multipart/form-data POST requests. It will append the ns_conn form ns_set with additional keys - two for each uploaded file. These are ''fileUploadFormFieldName''.'''content-type''', which is the content type as specified by the client, followed by ''fileUploadFormFieldName''.'''tmpfile''', which is the location of a temporary file containing the transmitted file content. The temporary file name is generated by [[ns_tmpnam]] and a script registered by [[ns_atclose]] deletes the temporary file when the connection is closed.

'''NOTES'''
: Here is one way to prevent the processing of large files:

set content_length [ns_set iget [ns_conn headers] content-length]
if {$content_length eq "" || $content_length > 1000000} {
# return some error message about file too big
}

''What happens if the client sends a false Content-Length: header?''

''Is there a way to limit the size of an incoming POST before the files are saved to the file system?''

See [[Annotated AOLserver Configuration Reference]]

ns_param maxinput [expr 5 * 1024 * 1024] ;# Maximum file size for uploads in bytes, default is 1MB, new in AOLserver 4.01

'''SEE ALSO'''

: [[ns_getformfile]], [[ns_queryget]], [[ns_set]]

----

[[Category:Documentation]] - [[Category:Core Tcl API]]

AOLserver Wiki

2010-02-24T22:21:04Z

Josephbui: Undo revision 5677 by HelenArchibald (Talk)

AOLserver Wiki

2010-01-19T17:28:28Z

Josephbui: Undo revision 5660 by Shacywayne (Talk) link spam

Ns schedule daily

2009-12-18T14:57:59Z

Josephbui: Corrected spelling of Daylight Saving Time

Man page: http://aolserver.com/docs/tcl/ns_schedule_daily.html

----

'''NAME'''

: ns_schedule_daily - Schedule a script to run daily at a certain time

'''SYNOPSIS'''

: '''ns_schedule_daily''' ''?-once? ?-thread? hour minute script''

'''DESCRIPTION'''

: 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.

: '''NOTE:''' ''hour'' and ''minute'' are specified in local time. Beware of Daylight Saving Time shifts affecting the time of day when the script will execute.

'''EXAMPLES'''

% set id [[ns_schedule_daily -once 5 35 { ns_log notice "It is now 5:35 AM." }]]
123

% ns_unschedule_proc $id

'''SEE ALSO'''

: [[ns_after]], [[ns_info]] scheduled, [[ns_pause]], [[ns_schedule_proc]], [[ns_schedule_weekly]], [[ns_unschedule_proc]]

----

[[Category:Documentation]] - [[Category:Core Tcl API]]

Ns schedule daily

2009-12-18T14:56:47Z

Josephbui: link spam

Man page: http://aolserver.com/docs/tcl/ns_schedule_daily.html

----

'''NAME'''

: ns_schedule_daily - Schedule a script to run daily at a certain time

'''SYNOPSIS'''

: '''ns_schedule_daily''' ''?-once? ?-thread? hour minute script''

'''DESCRIPTION'''

: 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.

: '''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.

'''EXAMPLES'''

% set id [[ns_schedule_daily -once 5 35 { ns_log notice "It is now 5:35 AM." }]]
123

% ns_unschedule_proc $id

'''SEE ALSO'''

: [[ns_after]], [[ns_info]] scheduled, [[ns_pause]], [[ns_schedule_proc]], [[ns_schedule_weekly]], [[ns_unschedule_proc]]

----

[[Category:Documentation]] - [[Category:Core Tcl API]]

Ns sendmail

2009-12-18T14:50:40Z

Josephbui: link spam

AOLserver Wiki

2009-12-18T14:48:50Z

Josephbui: link spam

Category User Group

2009-11-30T16:33:23Z

Josephbui: Redirecting to Category:User Group

#REDIRECT [[Category:User Group]]

Category:User Group

2009-11-30T16:32:38Z

Josephbui:

Purpose: To provide an index to AOLserver User Groups on this Wiki.

----

To see a list of all AOLserver User Groups on this Wiki, click on the above title.

To add a page to this category, add a link to this page, e.g., <nowiki>[[Category:User Group]]</nowiki>.

Category:User Group

2009-11-30T16:31:44Z

Josephbui: New page: Purpose: To provide an index to AOLserver User Groups on this Wiki. ---- To see a list of all AOLserver User Groups on this Wiki, click on the above title. To add a page to this categor...

Northern Virginia AOLSUG

2009-11-30T16:30:13Z

Josephbui:

Initially AOL has volunteered their facilities to hold the sessions.

If anyone is still interested in a users' group, contact [[User:Josephbui]]. The training room at my office can be reserved (near DuPont Circle in DC). It can also be reserved for an AOLserver [http://aolserver.meetup.com/cities/us/dc/washington/ meetup].

While eventually we hope the community will participate to the extent where it
doesn't rely on any individual, Initially the session talks will be led by
[[Carl Garland]].

'''Format for AOLSLUG typical Meeting'''
* First Hour : Basics/Core

This portion of the meeting will be for beginners/people that are interested
in basic topics and should allow some time for question/answer about
general AOLserver concepts.
* Second Hour : Main Meeting
** Current Events in AOLserver
** 1-2 talks given by AOLserver community members

These could be either discussion of topics or possibly a demonstration
of an AOLserver project that members have created.
** Wrap-up, general questions
* Followup festivities (beer optional)

'''Proposed 1st Meeting Date/Time'''

Please respond to when would be the best date/time for the first NOVA AOLSLUG
meeting. Future meetings will hopefully be held at every month or two depending
on community feedback.

Votes for particular day/night of week:
* Monday night
* Tuesday night
* Wednesday night - Carl Garland, Patrick O'Leary, Joseph Bui
* Thursday night
* Friday night
* Saturday
* Sunday

Anticipate the meeting will be held once/monthly or bimonthly.

'''Proposed 1st Meeting Agenda'''

Until we get feedback and volunteers for leading future session the initial
first session will consist of the following agenda unless feedback desires
different topics:
* Basics/Core: Installing and Building AOLserver
* Main Meeting: AOLserver and HTTPS, OpenSSL

Hopefully the AOLserver meetings can meet the needs of beginners in addition
to providing an outlet for users to discuss advanced issues and share
current undergoing endeavors.

'''Proposed Topics for Basics/Core'''
* Installing and Building AOLserver
* AOLserver configuration file
* Scheduled Procs
* Control Port
* Logging

'''Proposed Topics for Main Meeting'''
* AOLserver and HTTPS, OpenSSL
* AOLserver and Java Options
* Building your own Module
* Running nsd process through debuggers
* Web Services

'''AOLserver Projects in the Wild'''
* AOLserver dashboard (Jay Rohr)
* PGDiff ([[Carl Garland]])

----

[[Category:User Group]]

Northern Virginia AOLSUG

2009-11-30T16:29:12Z

Josephbui:

User:Josephbui

2009-11-30T15:57:20Z

Josephbui:

Joseph Bui used to work as an TCL developer in Washington, DC... unfortunately, the company I work for was purchased by a Java shop, so I don't use AOLserver or TCL for work anymore.

== Pages To Delete ==

I'm changing the content of all pages that I find that are spam or clearly non-AOLserver related content to redirect to [[Delete this page]]. Thus, you should be able to find them as broken redirects [[Special:BrokenRedirects]] or by looking for back links [[Special:Whatlinkshere/Delete_this_page]].

[[Category:Person|Bui, Joseph]]

Joseph Bui

2009-11-30T15:55:20Z

Josephbui: Redirecting to User:Josephbui

#REDIRECT [[User:Josephbui]]

User:Josephbui

2009-11-30T15:53:23Z

Josephbui:

Former AOLserver user... unfortunately, the company I work for was purchased by a Java shop.

== Pages To Delete ==

I'm changing the content of all pages that I find that are spam or clearly non-AOLserver related content to redirect to [[Delete this page]]. Thus, you should be able to find them as broken redirects [[Special:BrokenRedirects]] or by looking for back links [[Special:Whatlinkshere/Delete_this_page]].

[[Category:Person]]

Category:Modules

2009-11-30T15:52:01Z

Josephbui: New page: Purpose: To provide an index of pages describing AOLserver and TCL modules. To get a list of pages describing AOLserver and TCL modules, see the list below. To add a page to this categor...

Purpose: To provide an index of pages describing AOLserver and TCL modules.

To get a list of pages describing AOLserver and TCL modules, see the list below.

To add a page to this category, add a link to this page, e.g., <nowiki>[[Category:Modules]]</nowiki>.

Category:Documentation

2009-11-30T15:50:45Z

Josephbui: New page: Purpose: To provide an index of pages documenting AOLserver. To get a list of pages documenting AOLserver, see the list below. To add a page to this category, add a link to this page, e....

Purpose: To provide an index of pages documenting AOLserver.

To get a list of pages documenting AOLserver, see the list below.

To add a page to this category, add a link to this page, e.g., <nowiki>[[Category:Documentation]]</nowiki>.

User:Josephbui

2009-11-30T15:47:33Z

Josephbui:

User:Josephbui

2009-11-30T15:17:16Z

Josephbui:

I'm changing the content of all pages that I find that are spam or clearly non-AOLserver related content to redirect to [[Delete this page]]. Thus, you should be able to find them as broken redirects [[Special:BrokenRedirects]] or by looking for back links from that currently deleted page.

User:Josephbui

2009-11-30T15:14:49Z

Josephbui: New page: The following pages were entirely spam or non-AOLserver related content. They need to be deleted. I already deleted all the content. * Aren¡¯t_these_UGGS_you_EVER_did_see? * [...

The following pages were entirely spam or non-AOLserver related content. They need to be deleted. I already deleted all the content.

* [[Aren¡¯t_these_UGGS_you_EVER_did_see?]]
* [[The_Do¡¯s_Don¡¯ts_of_Ugg_Boots]]

AOLserver Wiki

2009-11-30T14:56:23Z

Josephbui: more link spam

'''[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.'''

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]].

== Topics of Conversation ==

* [[What is AOLserver]]?
* What [[Web Applications for AOLserver]] would you like to see?
* What [[AOLserver Bugs and Problems]] are you experiencing?
* What features does AOLserver need? Add them to the [[AOLserver Wishlist]].

* [[What's new in 4.5]] -- New features in version 4.5 of AOLserver. This is the current major release of AOLserver.

== AOLserver Resources: ==

* [[Downloads]] -- Access to various AOLserver files and resources.
* [[Modules]] -- Complete list of '''over 70''' AOLserver extension modules and other [[AOLserver Contributed Software]].
* [[Toolkits]] -- Everything you need to build a complete website, fast.
* [[Languages]] -- Build websites in a varierty of different programming languages.
* [[Documentation]] -- Tcl and C API references, tutorials and guides.
* [[FAQ]] -- Frequently Asked Questions about AOLserver.
* [[AOLserver Improvement Proposals]]
* The [[AOLserver Cookbook]] -- A collection of questions, and code examples to answer them.
* [[AOLserver Packages]] -- Binary distributions of AOLserver in popular package management formats.
* [[Useful Links]]
* [http://panoptic.com/wiki/aolserver/Special:Recentchanges?feed=rss RSS 2.0 syndication] of this wiki's recent changes.

== Developers' Guide (A Work In Progress) ==

* [[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.

== AOLserver Community ==

* The AOLserver project [[Roadmap]], as well as the planned [[Features]] and changes.
* The [[People]] who work on and contribute to AOLserver, organized into [[Project Teams]].
* 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.
* There's also an [http://www.livejournal.com/community/aolserver/ AOLserver LiveJournal community].
* [[Sites That Run On AOLserver]]
* The [[OpenACS]] Project.
* The [[ProjectOpen]] Project (project management based on [[OpenACS]])
* [[AOLserver User Groups]]
* [[AOLserver Jobs]]

== AOLserver Core Developers ==

* [[Vision Statement]]
* [[CVS Commit Guidelines]]
* [http://www.aolserver.com/docs/devel/tech/standards.html AOLserver Engineering Standards Manual]

__NOTOC__

Ns unschedule proc

2009-11-30T14:50:15Z

Josephbui: Undo revision 5596 by VervoidsTerror (Talk) link spam

Man page: http://aolserver.com/docs/tcl/ns_unschedule_proc.html

----

'''NAME'''

: ns_unschedule_proc - Unschedule a previously scheduled script

'''SYNOPSIS'''

: '''ns_unschedule_proc''' ''id''

'''DESCRIPTION'''

: This command unschedules a previous scheduled script. '''NOTE:''' Current behavior is to silently return without error if the ''id'' doesn't represent a currently scheduled ID.

'''EXAMPLES'''

% set id [[ns_schedule_proc -once 60 { test }]]
123

% ns_unschedule_proc $id

'''SEE ALSO'''

: [[ns_after]], [[ns_info]] scheduled, [[ns_pause]], [[ns_resume]], [[ns_schedule_proc]], [[ns_schedule_daily]], [[ns_schedule_weekly]]

----

[[Category:Documentation]] - [[Category:Core Tcl API]]

AOLserver Wiki

2009-11-30T14:47:37Z

Josephbui: link spam

AOLserver Wiki

2009-11-27T14:52:27Z

Josephbui: Undo revision 5597 by Akshay blizz (Talk)

What is AOLserver

2009-11-23T15:06:37Z

Josephbui: Undo revision 5564 by Daniel (Talk)

From the [[AOLserver Wiki]] home page:

: '''AOLserver''' is a high performance web server with a powerful customization API.

From the [[FAQ]]:

: '''AOLserver''' is [http://www.corp.aol.com/ America Online]'s Open Source web server. '''AOLserver''' is the backbone of the largest and busiest production environments in the world.

: '''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.

It has been ported to many Unix-derived platforms, as well as to Windows. A list is in the [[FAQ]] under "''What platforms does AOLserver support?''"

Interestingly, some people (like [http://www.panoptic.com/technologies.html Panoptic] - the hosts of this wiki) classify AOLserver not as a "web server" but as an "application server." YMMV.
Maybe it's best to classify it as a programming environment for generating dynamic web content under heavy load conditions?

In any case, AOLserver serves HTTP -- web pages -- containing the usual static files as well as ''ADP'' (''A''OLserver ''D''ynamic ''P''ages) containing TCL intermixed with HTML. The parsing and execution of the TCL code occurs "within" the server, rather than being transferred out through a CGI interface to another programming environment. The [http://www.apache.org/ Apache] web server running the [http://perl.apache.org/ mod_perl] interface module for Perl scripting is about the closest comparison. The reduced overhead makes for better performance and allows for a higher maximum transaction volume (number of "hits") with the same hardware system.

----

[[Eliyahu]] adds:

All of those fancy words sound very fine and impressive, but what do they really mean? :-)

: ''customization API'': an ''A''pplication ''P''rogramming ''I''nterface allows different software modules ("applications") to exchange data with each other -- '''AOLserver''' can be customized

: ''Open Source'': the source code of the program is "open" -- freely available to be studied, installed, or modified -- and specifically licensed (by the [[AOLserver Public License]]) to prevent it from being converted into "proprietary" software; the [http://www.opensource.org/ Open Source Institute] advocates and tries to standardize this licensing approach

: ''multithreaded'': different parts ("threads") of the program can be run simultaneously and/or in different orders without getting "''tangled''" -- important when there are multiple processors in a server cluster and/or long-running pages that need to be repeatedly served

: ''Tcl-enabled'': the "native" programming language for dynamic page content is '''Tcl''' [http://www.tcl.tk/] [[User:64.236.208.25|64.236.208.25]]
: [[[Note that modules for other web programming [Languages]] such as [[PHP]], [[Java]], and [[Perl]] are also available, or under development]]

: ''massively-scalable'': pages which run / are served on a small computer will act the same way when run / served on "large scale" hardware -- if you need to serve ''LOTS'' of pages at one time, or with lots of database action talking to multiple servers in a cluster, then '''AOLserver''' is good for you

: ''extensible'': a well-defined set of interfaces (API's) lets you add new modules to implement new features, and thereby "extend" the server's operation

----

[[Category Tutorial]]

Ns time

2009-11-23T15:06:34Z

Josephbui: Undo revision 5569 by Daniel (Talk)

<manpage>ns_time</manpage>

'''NAME'''

: ns_time - Perform various time-related functions

'''SYNOPSIS'''

: '''ns_time''' ''?option? ?arg arg ...?''

'''DESCRIPTION'''

: This command provides various time-related functions. The legal ''option''s (which may be abbreviated) are:

* '''ns_time adjust''' ''time''

: Adjusts ''time'' so that it is within the valid range of values for a time. ''(TODO: Figure out how this is actually useful.)''

* '''ns_time diff''' ''time1 time2''

: Computes the time difference between ''time1'' and ''time2''. It does this by subtracting ''time2'' from ''time1'' and returns a string in "sec:usec" format. Put the later time first to get the proper result.

* '''ns_time get'''

: Returns the current time in "sec:usec" format.

* '''ns_time incr''' ''time sec ?usec?''

: Increments ''time'' by ''sec'' seconds and optionally ''usec'' microseconds. Returns a string in "sec:usec" format.

* '''ns_time make''' ''sec ?usec?''

: Returns a string in the form "sec:usec". ''usec'' defaults to zero. If ''usec'' is zero, the colon and ''usec'' are not returned. If ''sec'' is zero, however, it is returned as part of the time string.

* '''ns_time seconds''' ''time''

: Parses a time in "sec:usec" format and returns the seconds portion.

* '''ns_time microseconds''' ''time''

: Parses a time in "sec:usec" format and returns the microseconds portion. It assumes zero microseconds if ''time'' only contains seconds.

'''NOTES'''

: All times are relative to 00:00:00 UTC, January 1, 1970 aka the Unix epoch. '''ns_time''' called with no option returns the current time in seconds.

'''EXAMPLES'''

% ns_time
1087006685

% set time [ns_time get]
1087013247:598897

% ns_time seconds $time
1087013247

% ns_time microseconds $time
598897

% set time2 [ns_time incr $time 5 30]
1087013252:598927

% ns_set diff $time2 $time
5:30

% set time3 [ns_time make 1087013240 598890]
1087013240:598890

% ns_time diff $time $time3
7:7

% ns_time diff $time3 $time
-8:999993

% set time3 [ns_time incr $time3 7 7]
1087013247:598897

% ns_time diff $time $time3
0

'''SEE ALSO'''

: [[ns_fmttime]], [[ns_gmtime]], [[ns_httptime]], [[ns_localtime]], [[ns_parsehttptime]], [[ns_parsetime]]

[[Category:Core Tcl API]]

OpenACS

2009-11-23T15:06:25Z

Josephbui: Undo revision 5573 by Daniel (Talk)

http://openacs.org/

OpenACS is an advanced toolkit for building scalable, community-oriented web applications. If you're thinking of building an enterprise-level web application, OpenACS is a solid, proven foundation that will give you a 3-6 month headstart.

Browse the code from a running system: http://openacs.org/api-doc/

AOLserver Contributed Software

2009-11-23T15:06:15Z

Josephbui: Undo revision 5574 by Daniel (Talk)

The AOLserver webserver can be extended in a couple of ways: [[Modules]] can be written using
the builtin [[C API]] or [[Tcl API]], or single pages can be written using either [[Tcl pages]] or [[ADP]]
pages. If you load one of the language modules, you will also be able to use your favourite
programming language to extend the AOLserver.

A complete list of the modules available, including database drivers, wrappers for popular C
libraries, utilities, and other extension [[languages]] is available on the [[Modules]] page.

''Provide links to ADP page creation etc.''

CVS Commit Guidelines

2009-11-23T15:06:07Z

Josephbui: Undo revision 5563 by Daniel (Talk)

In order to achieve our [[Vision Statement]], the AOLserver Project solicits contributions from any interested party. There are a limited number of [http://sourceforge.net/project/memberlist.php?group_id=3152 AOLserver Project Members] for the AOLserver Project hosted at SourceForge who have access to accept and commit these contributions, and this document outlines the general policies governing this activity.

----

'''1. Everyone who has CVS commit access, has CVS commit access.'''

Obviously true, but what does this really mean? It means that if you were given CVS commit access, most likely it was intentional and the interpretation of that action should be obvious: it has been acknowledged that the project wishes you to commit changes to the project.

'''2. Who grants CVS commit access?'''

While there are currently a number of Project Administrators, any of whom technically can grant others CVS commit access, the current Project Owner should be the only person to grant new members CVS commit access. There is no guidelines for deciding who to grant and not grant such access; the decision is solely left to the discretion of the current Project Owner.

'''3. I have CVS commit access and someone has contributed a patch which fixes a bug. Should I just go and merge it in and commit?'''

This is probably the hardest question to answer. Use the answer here as only a limited guideline to help you decide, and not as the authoritative rules governing this decision.

In the case of a patch which fixes a bug, ensure that the bug is documented by being filed in the [http://sourceforge.net/tracker/?group_id=3152&atid=103152 SourceForge Bug Tracker] first. This gives others a chance to investigate the bug and comment on it. The contributed patch may fix the bug, but there may be other solutions that are better and should be considered. Sometimes, the fix is trivial: it's still useful to have the bug documented for future review of past changes and bug fixes.

It's important that changes do not simply get merged in and committed without testing. If you wish to commit a change, do not do so unless you're also willing to commit the necessary time and resources necessary to test it. Sometimes, this just isn't feasible: use your best judgement, but it should generally be an exception and not the rule that changes get committed untested.

Finally, if you are a Project Admin., assign the bug to yourself to indicate that you're taking ownership of it. Otherwise, append a comment indicating that you wish to do so and request the bug be assigned to you. Once you are owner of the bug, proceed with merging in the change and testing to ensure the bug has been fixed. (Once a regression test suite has been developed, ensure all regression tests pass as well.) After committing the change, append a note to the bug indicating that you did apply the change and that you committed it.

'''4. What about feature enhancement patches? I think the feature is desirable, can I commit the change?'''

Like #3 above, this is only a suggestion and ultimately the decision should be made using your best judgement. However, here are some guidelines you may want to consider:
* Every line of code added increases the overall maintenance burden of AOLserver. While perceived to be small in some cases, there is a non-zero cost, however small it might be. Just because a feature has value does not mean it's valuable enough to be added to AOLserver.
* A feature that seems easy to implement today may make adding other new features or changing existing features more difficult tomorrow.
* Once a feature is implemented a particular way and people begin to use it, especially once they've deployed it into a production environment, it is very important to carefully maintain backwards compatibility. An inadequately thought out implementation may result in the need to break backwards compatibility. It is worth deferring adding such a feature until the design has clear signs of longevity rather than adding it in an incomplete state and then having people rely on it.
* Every new feature is an opportunity to add new bugs. Is this feature worth the risk?
* Does this feature help bring AOLserver closer to meeting its intended goals from the [[Vision Statement]]?
* Am I ready to be responsible for defending my decision to commit this change with my peers? If the feature turns out indeed have negative impact, do I feel comfortable with the responsibility for causing it? Do I have the time to make the necessary corrections to make things right and support my decision?
* Do I feel this feature has been adequately discussed with my peers? Have I given adequate consideration to all the reasons why the change request shouldn't be accepted? If people are voicing strong opinions against the change, do I really understand why?

If you still feel the feature should be added, then remember #1. Generally, follow a similar procedure as outlined in #3: ensure an RFE has been filed in the [http://sourceforge.net/tracker/?group_id=3152&atid=353152 SourceForge Feature Request Tracker] for people to discuss the request; assign the RFE to yourself or append a comment requesting a Project Admin. do so; merge the change in and test as much as you can; (once an automated test framework is in place, ensure you implement adequate tests to cover the new feature); commit your change and append a note to the RFE indicating you did so.

'''5. I hate to admit it, but I don't want CVS access anymore. What do I do?'''

Inform the current Project Owner and the access will be removed.

'''6. Someone committed a change and I feel it should be backed out. Can I do it?'''

See #1 above. It applies in the forward direction as well as backward. Everyone who has CVS commit access, has CVS commit access -- everyone can back out anyone else's change. However, before you do back out someone else's change, you should consider the list of questions in #4 above before doing so, especially:
* Am I ready to be responsible for defending my decision to commit this change with my peers? If the feature turns out indeed have negative impact, do I feel comfortable with the responsibility for causing it? Do I have the time to make the necessary corrections to make things right and support my decision?

If you still feel it's appropriate to back out someone's change, try and discuss the reasons why you feel this way and see if others agree. Perhaps you can persuade the original committer to either back out the change, or find alternate solutions. However, if backing out the change is the correct way to proceed, then do it.

Ns uuencode

2009-11-23T15:06:02Z

Josephbui: Undo revision 5572 by Daniel (Talk)

Man page: http://aolserver.com/docs/tcl/ns_uuencode.html

----

'''NAME'''

: ns_uuencode - Binary-to-text encoding using "htuu" encoding

'''SYNOPSYS'''

: '''ns_uuencode''' ''string''

'''DESCRIPTION'''

: This command performs a binary-to-text encoding on ''string''. There is an arbitrary limit of 48 bytes for the input ''string''. The encoded string will be approximately 33% longer than the original.

: '''NOTE:''' This is HTTP-style uuencoding/uudecoding which is sometimes called "htuu" (see [http://www.faqs.org/rfcs/rfc1113.html RFC 1113, 4.3.2.4 Step 4 Printable Encoding]). It is not compatible with the format used by the Unix uuencode/uudecode commands, nor is it base-64 encoding.

: For base-64 encoding, consider using the base64 Tcl package in tcllib.

'''EXAMPLE'''

% ns_uuencode "Test string"
VGVzdCBzdHJpbmc=

'''SEE ALSO'''

: [[ns_uudecode]], tcllib base64 [http://tcllib.sourceforge.net/]

----

[[Category Documentation]] - [[Category Core Tcl API]]

Project Teams

2009-11-23T15:05:55Z

Josephbui: Undo revision 5571 by Daniel (Talk)

The AOLserver Project is made up of several teams. Each team is responsible for carrying out their part of the overall project's activities.

If you wish to contribute to the AOLserver Project, contact the appropriate team leader(s) in the areas in which you wish to contribute.

'''Core Development Team'''

This team is responsible for maintaining the core code that makes up AOLserver.

''Team Leader:'' [[Dossy Shiobara]]

'''Quality Assurance Team'''

This team is responsible for ensuring that AOLserver continues to be a high quality software product.

''Team Leader:'' TBA

'''Documentation Team'''

This team is responsible for maintaining all relevant documentation for all supported releases of AOLserver.

''Team Leader:'' TBA

'''Evangelism Team'''

This team is responsible for bringing AOLserver to new audiences, doing competitive and comparative analysis of AOLserver with other solutions, identifying appropriate ways of spreading the word about AOLserver to increase its adoption, etc.

''Team Leader:'' TBA

Vision Statement

2009-11-23T15:05:52Z

Josephbui: Undo revision 5570 by Daniel (Talk)

: ''"I believe that the server can now do a great job at a reasonable number of tasks rather than an OK job at a huge number of tasks," Nachman said.'' [http://news.com.com/2100-1023-228252.html]

[[Dossy]] 28aug2004: There's many interpretations of what a "mission statement" and a "vision statement" should be. I define them thusly: a mission statement is a short, concise and recitable expression of purpose; a vision statement is a description or vision of what the end result might look like once the mission has been completed. Keep these definitions in mind when reading the mission statement and vision statement below.

'''Mission Statement'''

Our mission is to provide the best platform for rapidly developing web applications and infrastructure where high performance, scalability and availability are must-have requirements.

'''Vision Statement'''

(these are an unrefined collection of thoughts at the moment)
* rapid development by using Tcl, a high-level scripting language
* flexibility of using low level C or high-level Tcl
* available as open source software
* modularized component architecture of supporting infrastructure services for building applications
* enable simple solutions to common problems, especially for difficult problems

----

'''Comments:'''

I think AOLServer should be a high-speed ADP processing engine. There's already a swiss-army knife webserver, it's called Apache. There are static webservers that are faster than AOLServer and Apache (think thttpd). There are even other high-performance general purpose webservers, like Zeus. AOLServer is particularly good at generating dynamic pages fast. I would move more towards making AOLServer a dynamic component in web environments - like as a FastCGI server, and/or as a set of Tcl helpers and executables and such that could be tied in to mod_dtcl on Apache, or other ways of being integrated into other enterprise web environments. - [[Brady]]

[[Dossy]] 27aug2004: This page should probably be titled "Project Charter" and contain a mission statement, a vision statement, goals, etc.

AOLserver Cookbook

2009-11-23T15:05:47Z

Josephbui: Undo revision 5568 by Daniel (Talk)

A collection of questions, and code examples to answer them.

Add your questions here. Answers should be placed below the question. Place a horizontal line ("----") between questions. Please keep this text before the first question.

__TOC__

----

== Limiting bandwidth ==

Is there a simple way to limit bandwidth per connection/ip???

: There's no simple way of doing it, i.e., no configuration option you can set. If I had to implement this, I'd use NSV's and [[ns_register_filter]] to keep track of bandwidth consumed by each client IP which can act as an all-or-nothing mechanism. However, what might be interesting to implement in the socket driver is a setting to control the rate at which bytes are written back to the socket, perhaps configurable per request, so that large HTTP responses don't soak up your upstream bandwidth. We should keep this in mind for a future version of AOLserver. ''-- [[User:Dossy|Dossy]] 20:06, 4 November 2005 (EST)''

One more question... How can I read output buffer inside function registered as postauth filter?
And how can I stream it? ns_adp_puts cannot be used inside filters... ns_return would return all data at once. I assume that per connection limit would look like this:
<pre>
proc ..... {
ns_adp_stream
set data [get output content buffer]
set data_length [output buffer size]
set block_size 4096
for {set i 0} {$i < $data_length} {incr i $block_size} {
send_to_client [string range $data [expr $block_size*$i] [expr $block_size*[expr$i+1]]]
sleep 1
}
ns_returnok
return filter_return
}
</pre>
I want to limit only one vhost so nssock limit would be too much;)

: First, you don't want to turn [[ns_adp_stream]]'ing on. Getting the size of the ADP output buffer can be done using [[ns_adp_tell]] and getting the contents with [[ns_adp_dump]]. I guess you could [[ns_adp_trunc]] the output buffer to clear it, then slowly write the contents back using [[ns_write]]. You'd also then need to look at [[ns_conn]] '''outputheaders''' to make sure that you wrote the proper HTTP response ... ah, but I don't know if you can get the HTTP response status code somehow. I still think doing it in nssock is probably the best place, even with vhosts -- I'd make it a preauth or postauth filter that sets the configuration for the response and then have nssock be responsible for ensuring the response is written at that rate. ''-- [[User:Dossy|Dossy]] 07:24, 8 November 2005 (EST)''

ns_adp_tell inside postauth filter:
Error: This function cannot be used outside of an ADP
what's more, i use ns_returnfile inside some adp code and if i use ns_adp_tell after it, it returns 0 (this adp only returns file, no adp_puts or write).
Unfortunetly i think there is no other solution then implement it inside nssock or implement some tcl code to manipulate all output buffer.

I use this code for big files... some time I'll add per ip limit, now it's for connection.
<pre>
proc returnfile { file } {
set filefp [open $file r]
fconfigure $filefp -translation binary
set data_length [file size $file]
set block_size 4096

ns_write "HTTP/1.0 200 OK
MIME-Version: 1.0
Content-Type: [ns_guesstype $file]
Content-Length: $data_length

"
while { ! [eof $filefp] } {
ns_writefp $filefp $block_size
ns_sleep 1
}

ns_conn close
}
</pre>
Paul Bukowski
----

== Virtual server configuration ==

Is it possible to use wildcard '*' in domain name inside "ns/module/nssock/servers" section of aolserver4 config file? I would like to map all requests to *.somedomain.org to one virtual host...
Something like this doesn't work:

ns_section "ns/module/nssock/servers"
ns_param forum somedomain.org
ns_param forum somedomain.org:80
ns_param forum *.somedomain.org
ns_param forum *.somedomain.org:80
ns_param forum "*.somedomain.org"
ns_param forum "*.somedomain.org:80"

-Paul Bukowski

: ''2005aug15 [[Dossy]]: Unfortunately, no -- you currently can't use wildcards the way you want. Not yet, at least.''

Why won't you get some code for mass virtual hosts from http://naviserver.sourceforge.net/ ??
-PB

: Right now, to map a request to its (virtual) server, there's an O(n) search being done, but it's a "cheap" exact string comparison. To implement glob-style wildcard support, it'll become a more expensive (but possibly still "cheap" by most people's standards) glob-match comparison. When you're serving "n" requests per second (where "n" is small) the difference in cost is probably immeasurable, but when "n" is large, the cost is additive and possibly significant. It might be good if someone could benchmark the two and see what the real cost is. ''-- [[User:Dossy|Dossy]] 20:12, 4 November 2005 (EST)''

----

== Server-side Includes ==

Does anyone have some code to implement apache-compatible SSI (Server-side includes)? I have some old pages that use SSI that I'd like to move to my aolserver install but I don't have the time to rewrite them as ADPs.

: ''[[User:Dossy|Dossy]] 20:20, 4 November 2005 (EST)'': I make no representations or warranties about the safety (!) or correctness of the code I'm about to share, but it might get folks started on a proper implementation in the future. In particular, I didn't implement any commands other than "include" and I even implemented it "wrong" (not according to [http://hoohoo.ncsa.uiuc.edu/docs/tutorials/includes.html the specification]). If there's real interest in having a complete SSI implementation for AOLserver, I'd be willing to improve this code.

<pre>
ns_log Notice "ssi: registering SSI ADP tags"

proc ssi_include_tag {params} {
set param_count [ns_set size $params]
for {set i 0} {$i < $param_count} {incr i} {
set ssi_var_[ns_set key $params $i] [ns_set value $params $i]
}

if [info exists ssi_var_file] {
if {[ns_adp_argc] > 1} {
set basedir [lindex [ns_adp_argv] 1]
} else {
set basedir [ns_adp_dir]
}
if [regexp {^/} $ssi_var_file] {
set filename $ssi_var_file
} else {
set filename $basedir/$ssi_var_file
}
return [ns_adp_parse -file $filename $basedir]
}
}

ns_register_adptag {!--#include} ssi_include_tag

ns_log Notice "ssi: registering SSI ADP tags done"
</pre>

----

Is there a way to see only the errors (for example - 'variable' xxx not found? I seem to remember 2 logs - servername.log and servername-error.log? The version I have now - aolserver 3.2/ad1.2 only seems to give us servername.log - and all the error messages are mixed with the normal msgs - its very hard to debug!
[[dannyl50]]

The default/example config file did not have entries for both logs. The two sections you need look like (in old style notation):

[ns/parameters]
User=nsadmin
Group=nsadmin
ServerLog=/var/log/aolserver/servername-error.log
PidFile=/var/log/aolserver/nspid.servername
Home=/usr/bin/aolserver-3.3ad13

and

[ns/server/servername/module/nslog]
File=/var/log/aolserver/emp.log
LogCombined=On
MaxBackup=3
RollFmt=%Y-%m-%d-%H:%M
RollHour=0
RollOnSignal=On
RollLog=On

----

Howdy! Can someone tell me, in general terms, how they have implemented [[nsperm]]? It looks cool, but I am using a plain old database with names and passwords, and it is very easy. I would like the allow/deny functionality, can I have that without the username/password part? -- [[Ian Harding]]

''I've implemented [[nsperm]] to restrict access to specific URLs using HTTP authentication (the username/password dialog) and cookie-based (if they have the correct cookie, otherwise URL redirect them to a login page that may set the cookie).''
''The latter is done using a registered preauth filter. I chose to use [[nsperm]] over a database since [[nsperm]] (presumably) manages the authentication information in memory better than repeatedly hitting the database with authentication requests, but there's no reason''
''I couldn't have used a database to store username/password information. Does this answer your question?'' -- [[Dossy]]

Pretty much, although I started writing my app before I understood AOLServer, so I have a rather strange design that is good in some ways, bad in others. Keep in mind that this is a low activity app, no more than 20 concurrent users right now.

What I did was to create an [[ADP]] that has a big case statement. It calls functions to generate pages based on the 'task' value it is passed through POST. I have created a pretty complex app this way, not using [[ns_register_proc]] at all. I know now I should have. As I understand it, ns_register_proc lets you create a 'virtual' directory structure that actually just calls certain procedures based on the GET or POST requested URL. This is far more graceful than hitting my main adp which opens up the form data, looks at the 'task' value, and decides which procedures to call.

Given this lame structure, each time someone requests the main adp, I just check for a valid cookie and generate a login page if it's not there. After that, I have to set another cookie that is their 'access rights' which is then checked from within the procs that generate the pages. If I was doing it right, I could have registered a proc that would fire for all URLs in my virtual tree, checking your rights to the particular URL you reqested, and redirecting you if you are not allowed, right?

Thanks!!! -- [[Ian Harding]]

''I probably would've created an ADP per task, and then registered a preauth filter that checked for the cookie and redirected the user to the login page (outside the directory that the preauth filter covers''
''-- avoid funny redirection loops) if the cookie wasn't set properly.''
''If you don't want to create a separate ADP per task, you could have used ns_register_proc to create what you describe as "virtual pages" and still have the preauth filter kind of "sit in front" and handle the autehntication, keeping that logic seperate from your actual page generation code.'' -- [[Dossy]]

I started with a separate adp for each task, but I thought it would get out of hand quickly. I do think I will re-work the thing to use ns_register_proc and even do away with the few adp I do have. It seems far easier to maintain. In the meantime, I have to re-write all my SQL Server procedures in PostgreSQL PL/Tcl. That's why I want the [[nsfreetds]] module so badly, it buys me a little time!

Thanks for all your work! -- [[Ian Harding]]

----

''Speaking of [[nsfreetds]], did you try nsfreetds-0.1pre? Any luck? Any problems?'' -- [[Dossy]]

I just now tried it. I installed freetds with no trouble, compiled nsfreetds, modified my nsd.tcl [[config file]], added the datasource to interfaces, and all seems fine, except for that I always get "no access to pool "mypool" while executing "ns_db gethandle mypool" ..."

I must have missed something. I saw something in the README about setting $env(SYBASE) before starting nsd. Is this the same as the SYBASE=/usr/pkg/freetds I had to do even before the build of nsfreetds?

Thanks again... I feel like I am close.. -- [[Ian Harding]]

''Yes, the $env(SYBASE) means setting the SYBASE environment variable. To be safe, you can try this:''

$ cd /path/to/aolserver/install
$ SYBASE=/usr/pkg/freetds; export SYBASE
$ bin/nsd ...args...

''Check log/server.log to make sure that the nsfreetds driver is actually loading. You should see a lines like this at start-up:''

[30/May/2001:13:42:37][11838.1024][-main-] Notice: modload: loading '/home/aolserver-dev/bin/nsfreetds.so'
[30/May/2001:13:42:37][11838.1024][-main-] Notice: Ns_FreeTDS_DriverInit(freetds): Loaded Panoptic FreeTDS Driver v0.1-pre, built on May 21 2001 at 22:23:01.

''Are you getting an error in the [[server log]] instead?'' -- [[Dossy]]

I don't get an error, it seems to load nicely. I can post or give you access to whatever files or output you would like to see, or an ssh login... -- [[Ian Harding]]

----

Another question: Global variables ([[nsv]]*). I am re-writing my app to use the [[ns_register_proc]] functionality versus my kludge where everything goes through an [[ADP]] that acts as a filter and traffic cop. I have figured out register filter and register proc, but seem not to be able to use [[ns_puts]] from within the procs. Is this right? Anyway, I had been using [[ns_adp_include]] in my filter/traffic cop page to put consistent headers/footers on my pages. I gather the more correct way (and only possible way with registered procs?) is to use global variables.

When do I initialize them? How do I use them? What are the caveats? W

Thanks, -- [[Ian Harding]]

''Have you started by reading the NSV documentation?'' -- [[Dossy]]

Of course not 8^0 That would be too easy! I will... -- [[Ian Harding]]

OK, I read it. It's too easy. I use it for header, footer, and client side script html, which I stuff into html variable before returning it. I would like the filter option we talked about in the chat which would prepend or append html automatically, but this will do. -- [[Ian Harding]]

----

How hard would it be to add an HTTPS equivalent of Ns_FetchURL?

''If you can build shared libraries on your target platform with OpenSSL, it probably wouldn't be too hard. The trick would be writing enough stub code that can be loaded via the Tcl "load" proc so that you could access the OpenSSL-based https client from your Tcl code. Is there a lot of demand for this? I could probably bang something out as an initial attempt.'' -- [[Dossy]]

[[Scott Goodwin]]'s [[nsopenssl]] now contains client side https functionality.

----

Am I a brick, or does ns_register_proc just plain not work with more than one argument for the proc? I have tried the following code on both aolserver 3.2 running on NT4 and aolserver 3.4 on NetBSD 1.5. It fails to register the proc even once, if I try to register it with more than one argument anywhere else.

ns_register_proc GET /foo1 foo 1
ns_register_proc GET /foo2 foo 1 2
ns_register_proc GET /foo3 foo 1 2 3

proc foo { conn one {two 22} {three 333}} {
ns_return 200 text/html "one is $one, two is $two, three is $three"
}

This must be something simple. I have already posted to the aolserver list but the listserv seems to have gone mad.

[[Ian Harding]]

''What are you trying to do? It appears you want to pass constant parameters to your procedures. If they are constants, why pass them? Since ns_register_proc calls are generally in the global scope (and sourced when nsd starts) even a parameter that appears to be a variable probably can/will not vary.''

''Presumably you need to get information from one page to another. That means formvalues unless your page is stateful (usually a bad idea). Check out the '''[[ns_conn]] form''' command to get yourself started.'' -- [[Jason Kane]]

----

OK, I'm using Windows 2000 SP2 and 3.4.1, and trying in vain to get Perl CGIs (legacy) to work. The scripts work outside of Aolserver, and work on AOLserver on Linux, but when I try inside the script to GET from myself (eg, GET http://localhost:8000/foo?bar=bas), I'm told "unknown protocol TCP", which is quite aggravating.

Does anyone have any experience administering AOLServer on Windows?

Thanks in advance!

-Bill

----

This is interesting, wy do you let me change your page?
I'm trying to find an example of how to get my data using:
set formdata [ns_conn form $conn]

-Jason

Because it's a wiki! A proc that gets posted variables includes the line you wrote there... then when you want to actually get the values, you can use something like

set myvar [ns_set get $formdata myvar]

where myvar is the name of the variable. There is also ns_queryget which looks like

set myvar [ns_queryget myvar defaultval]

This is handy because if there is no value, it will assign a default value.

Check out aolserver.com, they have extensive (although sometimes misleading) docs. If something the docs says should work doesn't, ask. It may be out of date.

[[Ian Harding]]

----

I don't know where else to share my code fragments, so here seems like as good a place as any. This one implements user public_html directories. It's based on someone else's stuff (I forget whose tho). It should really do something with unknown mime types, and should do a better job with errors like unknown users. It does honor directoryFile and adp maps in the config file.

It works by registering a procedure to /users that interprets the username and finds their directory. ns_register_proc doesn't allow wildcards other than in the last path element, so /~* wouldn't work. However that's not a problem for a filter, so there's a filter to take your /~user url and redirect it to /users/user

-JR

proc homedir { conn ctx } {
set url [ns_conn url $conn]
set user {}
set file {}
regexp {^/users/([^/]*)(/.*)?$} $url dummy user file
# ns_returnnotice 200 "url is $url user is $user, file is $file"
set userfile [getUserFile $user $file]
set type [ns_guesstype $userfile]
if {[string match "*[ns_config ns/server/[ns_info server]]/adp map]" $userfile]} {
# ns_log notice "adp parsing $userfile"
set cwd [pwd]
cd [file dirname $userfile]
# ns_return 200 text/html [ns_adp_parse -file $userfile]
set result [catch {ns_adp_parse -file $userfile} error]
if {$result} {
ns_return 200 text/html $error
} else {
ns_return 200 text/html $error
}
cd $cwd
} else {
switch $type {
"*/*" {
}
default {
ns_returnfile 200 $type $userfile
}
}
}

if {[catch {set fp [open $userfile]}]} {
ns_returnnotfound
return
}
}

proc getUserFile {user path} {
foreach tail [split ,[ns_config ns/server/[ns_info server] directoryfile] ,] {
set userfile "[glob ~$user]/public_html$path$tail"
if {[file exists $userfile] && ![file isdirectory $userfile]} {
return $userfile
}
}
ns_returnnotfound
# break
}

ns_register_proc GET /users/ homedir
ns_register_proc POST /users/ homedir
ns_register_proc HEAD /users/ homedir

proc userRedir {conn arg why} {
set url [ns_conn url]
regsub {^/~(.*)} $url {/users/\1} redir
ns_log notice "url is $url, redir is $redir"
ns_returnredirect $redir
return filter_break
}

ns_register_filter preauth GET /~* userRedir

----

Hi!

Does anybody know a graphing module for Aolserver/TCL, with e.g. bargraphs, linegraphs,... ?

-[[wiwo]]

''Yes: [[nsgds]], [[nschartdir]].''

----

Can I detect if the user pushes the Stop button in their browser in my TCL/ADP page?

Yes, although it's a kludge. ns_write will return zero if it cannot write because the connection has been lost. However, ns_write is not stupid enough to try writing when you give it nothing to write, and so you must send something to the client. To prevent this being rendered use HTML comments, e.g.

if {[ns_write "<nowiki></nowiki>"] == 0} {
# user hit the stop button, browser page was closed, or connection to client was lost.
}

[[Ximon Eighteen]]

----

== Generating random passwords ==

The following method can be useful to generate random passwords and/or password salts.

<pre>
# desired length of random string
set iStringLength 8

# characters allowed to appear in the string
set sAllowableCharacters "0123456789abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ"

# get length one time
set iAllowableCharacters [string length $sAllowableCharacters]

# begin random string as empty
set sRandomString ""

# loop until desired length is achieved
for {set ii 0} {$ii < $iStringLength} {incr ii} {

# get next random between 0 and length of allowed characters
set iRandomInt [ns_rand $iAllowableCharacters]

# retrieve this random character
set sRandomCharacter [string index $sAllowableCharacters $iRandomInt]

# append the character to our random string
append sRandomString $sRandomCharacter

}

ns_adp_puts "sRandomString: $sRandomString"
</pre>

---

== Customizing error pages ==

Edit your AOLServer's config file, and add the paths to the error pages as follows:

<pre>
#
# Internal redirects
#
ns_section "ns/server/${servername}/redirects"
ns_param 404 "/notfound.html" ;# Not Found error page
ns_param 500 "/servererror.html" ;# Server Error page
</pre>

---

== Fast caching of generated pages ==

You can use an adp page to handle a 404 (not found) error that generated exactly the page it was looking for. Conceptually this is similar to how tcl's autoloading using unknown works. From Bas Sheffers, via John Buckman.

from config.tcl:
<pre>
ns_section "ns/server/$server1/redirects"
ns_param 404 /404.adp
</pre>

404.adp:
<pre>
<% handle_404 %>
</pre>

Support procs:
<pre>
proc handle_404 {} {
set myurl [myurl]
set parts [split $myurl /]
set root [lindex $parts 1]

if {$root == "photo"} {
return [404_photo $parts]
} else {
ns_returnredirect "[myhost]/"
return
}

}

proc 404_photo {parts} {

set userid [file rootname [lindex $parts 2]]
set d [user_photo_data $userid]
if {$d == ""} {
set fn "/b/photo/unknown.jpg"
} else {
set fn "/b/photo/${userid}.jpg"
write_binary_file $fn $d
}
ns_returnfile 200 "image/jpeg" $fn
}

proc myurl {} {
return [lindex [split [ns_conn request]] 1]
}

proc photo_cache_dirty {userid} {
set fn "/b/photo/${userid}.jpg"
file delete $fn
}
</pre>

== Changing maximum upload file size ==

For aolserver 4.5 and higher, to change the maximum upload file size from the default value to a custom one, add a line like this to the server configuration file:

<pre>
ns_limits set default -maxupload [expr 25 * 1024 * 1024] ;# Maximum file size set to 25Mb
</pre>

== Return a file generated live ==

Example using the db_foreach function from OpenACS, for the sake of code readability:

<pre>
db_foreach get_mailing_addrs "

select company_name,
address,
city,
province_abbrev,
postal_code
from ce_members
order by company_name" {

append csv_text "\"$company_name\",\"$address\",\"$city\",\"$province_abbrev\",\"$postal_code\"\r\n"
}

ns_set update [ns_conn outputheaders] content-disposition "attachment; filename=\"member-addresses.csv\""

ns_return 200 application/octet-stream $csv_text
</pre>

AOLserver Bugs and Problems

2009-11-23T15:05:39Z

Josephbui: Undo revision 5565 by Daniel (Talk)

'''Bugs should be reported using the [http://sourceforge.net/tracker/?atid=103152&group_id=3152 SourceForge Bug Tracker] for the AOLserver project.'''

----

12 Jul, 2006

Hi,

I'm having a compilation error when trying to build AOLserver-4.5.0. It's the first time I use AOLserver, so its probably a silly problem. Can anyone help me?

cl /EHsc /W3 /nologo /c /MD /O2 /D "_WINDOWS" /D "TCL_THREADS=1" /D "WIN32"
/D "FD_SETSIZE=128" /D "NO_CONST=1" /D "_MBCS" /D "NDEBUG"
/I "C:\Pruebas\src\aolserver-4.5.0-src\include"
/I "C:\Pruebas\Tcl8.4.13\include" /c /Fodns.o
dns.c
dns.c
dns.c(258) : error C2065: 'NI_MAXHOST' : undeclared identifier
dns.c(258) : error C2057: expected constant expression
dns.c(258) : error C2466: cannot allocate an array of constant size 0
dns.c(258) : error C2133: 'buf' : unknown size
dns.c(278) : warning C4013: 'getnameinfo' undefined; assuming extern returning
int
dns.c(279) : warning C4034: sizeof returns 0
dns.c(280) : error C2065: 'NI_NAMEREQD' : undeclared identifier
dns.c(282) : warning C4013: 'gai_strerror' undefined; assuming extern
returning int
dns.c(325) : error C2079: 'hints' uses undefined struct 'addrinfo'
dns.c(331) : error C2224: left of '.ai_family' must have struct/union type
dns.c(332) : error C2224: left of '.ai_socktype' must have struct/union type
dns.c(333) : warning C4013: 'getaddrinfo' undefined; assuming extern returning
int
dns.c(340) : error C2037: left of 'ai_addr' specifies undefined struct/union
'addrinfo'
dns.c(340) : error C2198: 'ns_inet_ntoa' : too few actual parameters
dns.c(341) : error C2037: left of 'ai_next' specifies undefined struct/union
'addrinfo'
dns.c(343) : warning C4013: 'freeaddrinfo' undefined; assuming extern
returning int
NMAKE : fatal error U1077: 'cl' : return code '0x2'
Stop.
NMAKE : fatal error U1077: 'C:\Pruebas\Tcl8.4.13\bin\tclsh84t.exe' : return
code '0x1'
Stop.

I'm using aolserver-4.5.0 with Tcl8.4.13 in Windows XP. I compiled Tcl with the options threads and thrdalloc.

Thanks,

Miguel

----

Has anyone succesfully run 4.0.7 (or any other version) on SuSE 8 for AMD64? It appears to build OK (built against 64 bit build of Tcl 8.4.5) but when run throws a
NsTclInitObjs: sizeof(int) < sizeof(long)
Aborted
error

Thanks

Damien

[[Dossy]] 27jul2004 - ''Damien, [http://article.gmane.org/gmane.comp.web.aolserver/10802 Tomasz Kosiak] asked the same question on the AOLserver mailing list and [http://article.gmane.org/gmane.comp.web.aolserver/10804 Jim Davidson] responded that commenting out the failing check you experienced may be safe. Tomasz then [http://article.gmane.org/gmane.comp.web.aolserver/10809 replied] that he'd followed Jim's advice, and it seems to be working just fine. Once I get some time on a AMD64 system, I'll do some testing and commit the change. For now, you can either make the same change Tomasz did, or wait.''

---

I am having problems with [[ns_sha1]] returning sha1 hashes that differ from all other library implementations. -Caveman

* Can you provide a short snippet of sample code (incl. sample data, and what you get as output) from ns_sha1 as well as one other library implementation, so we might be able to identify where the difference is coming from? ''-- [[User:Dossy|Dossy]] 07:10, 3 December 2005 (EST)''

** Such information is on the linked [[ns_sha1]] page. --[[User:Caveman|Caveman]] 09:27, 3 December 2005 (EST)

AOLserver Wiki

2009-11-23T15:05:37Z

Josephbui: Undo revision 5557 by Daniel (Talk)

Ns getform

2009-11-23T15:05:31Z

Josephbui: Undo revision 5560 by Daniel (Talk)

Man page: http://aolserver.com/docs/tcl/ns_getform.html
----

'''NAME'''

: ns_getform - Return the connection formdata ns_set, copying multipart form data into temp files if necessary.

'''SYNOPSIS'''

: '''ns_getform''' ''?charset?''

'''DESCRIPTION'''

: This is a Tcl wrapper to '''[[ns_conn]] form''' that first calls [[ns_urlcharset]] if ''charset'' is specified. In addition, if the request contains multipart form submission, it copies each uploaded file content into a temp file and sets up data to allow access to these temp files using [[ns_getformfile]]. Otherwise, it generally behaves the same as ns_conn form, so see its documentation for more details.

: Use this for multipart/form-data POST requests. It will append the ns_conn form ns_set with additional keys - two for each uploaded file. These are ''fileUploadFormFieldName''.'''content-type''', which is the content type as specified by the client, followed by ''fileUploadFormFieldName''.'''tmpfile''', which is the location of a temporary file containing the transmitted file content. The temporary file name is generated by [[ns_tmpnam]] and a script registered by [[ns_atclose]] deletes the temporary file when the connection is closed.

'''NOTES'''
: Here is one way to prevent the processing of large files:

set content_length [ns_set iget [ns_conn headers] content-length]
if {$content_length eq "" || $content_length > 1000000} {
# return some error message about file too big
}

''What happens if the client sends a false Content-Length: header?''

''Is there a way to limit the size of an incoming POST before the files are saved to the file system?''

See [[Annotated AOLserver Configuration Reference]]

ns_param maxinput [expr 5 * 1024 * 1024] ;# Maximum file size for uploads in bytes, default is 1MB, new in AOLserver 4.01

'''SEE ALSO'''

: [[ns_getformfile]], [[ns_queryget]], [http://www.besttermpaper.com paper writing], [[ns_set]]

----

[[Category:Documentation]] - [[Category:Core Tcl API]]

ProjectOpen

2009-11-23T15:05:22Z

Josephbui: Undo revision 5559 by Daniel (Talk)

]project-open[ is a Web-based project management system for companies with 2-200 employees in the consulting, engineering, advertising, and translation sectors. ]po[ helps you to run your business by covering the entire project life cycle from sales (CRM-light), staffing, execution (timesheet, controlling, incidents, discussions, and file storage) to invoicing and payment.

The ]po[ architecture is designed for mission-critical applications with a rock-solid infrastructure based on [[AOLserver]] and [[OpenACS]].

== Use of AOLserver ==

There are about 1000 companies today (March 2007) running ]project-open[:

* About half of the companies use AOLServer 4.0.beta10 on Windows
* The other half uses AOLServer 3.3oacs on Linux
* There are a dozen or so installations on Solaris and BSD (Mac OS)

== ]project-open[ Modules ==

* [http://www.project-open.org/product/modules/pm Projects Management]: Project, Subprojects, Project Planning, Resource Planning, Project Tracking, integration with [http://sourceforge.net/projects/ganttproject/ GanttProject], Project Templates, ...

* [http://www.project-open.org/product/modules/finance Project Finance]: Timesheet, Exenses and Travel Costs, Invoicing (fixed & variable cost projects), Project Controlling, Financial Reporting, Profit & Loss, Accounting Export

* [http://www.project-open.org/product/modules/ Project Collaboration]: Wiki, Forum, Filestorage, Bug Tracker, Incident Management
* [http://www.mustuniversity.com/Schools-Majors/Business-and-Management-Masters-Degree.html MBA degree]
* [http://www.mustuniversity.com/Programs/Diploma/Graduate-Diploma.html graduate diploma]

== Links ==

* SourceForge: http://sourceforge.net/projects/project-open/
* Developers: http://www.project-open.org/
* Commercial: http://www.project-open.com/

ProjectOpen

2009-11-23T15:05:19Z

Josephbui: Undo revision 5558 by Daniel (Talk)

AOLserver Wiki

2009-11-23T15:04:07Z

Josephbui: Undo revision 5556 by Daniel (Talk)

'''[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.'''

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]].

== Topics of Conversation ==

* [[What is AOLserver]]?
* What [[Web Applications for AOLserver]] would you like to see?
* What [[AOLserver Bugs and Problems]] are you experiencing?
* What features does AOLserver need? Add them to the [[AOLserver Wishlist]].

* [[What's new in 4.5]] -- New features in version 4.5 of AOLserver. This is the current major release of AOLserver.

== AOLserver Resources: ==

* [[Downloads]] -- Access to various AOLserver files and resources.
* [[Modules]] -- Complete list of '''over 70''' AOLserver extension modules and other [[AOLserver Contributed Software]].
* [[Toolkits]] -- Everything you need to build a complete website, fast.
* [[Languages]] -- Build websites in a varierty of different programming languages.
* [[Documentation]] -- Tcl and C API references, tutorials and guides.
* [[FAQ]] -- Frequently Asked Questions about AOLserver.
* [[AOLserver Improvement Proposals]]
* The [[AOLserver Cookbook]] -- A collection of questions, and code examples to answer them.
* [[AOLserver Packages]] -- Binary distributions of AOLserver in popular package management formats.
* [[Useful Links]]
* [http://panoptic.com/wiki/aolserver/Special:Recentchanges?feed=rss RSS 2.0 syndication] of this wiki's recent changes.

== Developers' Guide (A Work In Progress) ==

* [[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.

== AOLserver Community ==

* The AOLserver project [[Roadmap]], as well as the planned [[Features]] and changes.
* The [[People]] who work on and contribute to AOLserver, organized into [[Project Teams]].
* Come join us in our [http://www.aolserver.com/chat/ online chat], or just read the [http://panoptic.com/aolserver/chat/ chat logs][http://www.mustuniversity.com/Programs/Degree/PhD-Degree.html phd degree]. You can participate on the chat either via IRC (irc.freenode.net:6667 #aolserver) or via AIM.
* There's also an [http://www.livejournal.com/community/aolserver/ AOLserver LiveJournal community].
* [[Sites That Run On AOLserver]]
* The [[OpenACS]] Project.
* The [[ProjectOpen]] Project (project management based on [[OpenACS]])
* [[AOLserver User Groups]]
* [[AOLserver Jobs]]
* [http://www.mustuniversity.com/Programs/index.asp Online degree program ]

== AOLserver Core Developers ==

* [[Vision Statement]]
* [[CVS Commit Guidelines]]
* [http://www.aolserver.com/docs/devel/tech/standards.html AOLserver Engineering Standards Manual]
* [http://www.superiorpapers.com/ custom term papers]
__NOTOC__