User talk:Caveman - Revision history

Dossy: New section: Sysop and Bureaucrat rights

2009-10-20T20:50:35Z

New section: Sysop and Bureaucrat rights

Caveman: /* AJAX/JSON support in AOLserver */ removed spammer link to "buy term papers"

2009-10-08T18:45:59Z

AJAX/JSON support in AOLserver: removed spammer link to "buy term papers"

Caveman: /* useful links */ removed spammer links

2009-10-08T18:45:24Z

useful links: removed spammer links

Caveman: /* AJAX/JSON support in AOLserver */

2006-01-01T16:05:27Z

AJAX/JSON support in AOLserver

Caveman: /* AJAX/JSON support in AOLserver */

2005-12-25T22:17:37Z

AJAX/JSON support in AOLserver

Caveman: AJAX/JSON support in AOLserver

2005-12-25T22:16:41Z

AJAX/JSON support in AOLserver

Caveman: corrected use of ns_dbquotevalue

2005-12-14T22:57:19Z

corrected use of ns_dbquotevalue

Caveman at 21:53, 14 December 2005

2005-12-14T21:53:13Z

Caveman: /* cleaned up old conversations */

2005-12-14T20:26:11Z

cleaned up old conversations

Caveman: /* useful links */

2005-12-14T20:20:52Z

useful links

← Older revision		Revision as of 20:50, 20 October 2009
Line 161:		Line 161:
	* [http://en.wikipedia.org/wiki/AJAX wikipedia article on AJAX]		* [http://en.wikipedia.org/wiki/AJAX wikipedia article on AJAX]
	* [http://rajshekhar.net/blog/archives/85-Rasmus-30-second-AJAX-Tutorial.html 30 second intro to AJAX]		* [http://rajshekhar.net/blog/archives/85-Rasmus-30-second-AJAX-Tutorial.html 30 second intro to AJAX]
		+
		+	== Sysop and Bureaucrat rights ==
		+
		+	Hi, Sam - I've granted you Sysop and Bureaucrat rights, so you can delete wiki pages and such. You seem to watch the wiki and police it for spam a lot more than I can these days. Thanks! -- [[User:Dossy\|Dossy]] 16:50, 20 October 2009 (EDT)

@@ Line 153: / Line 153: @@
 Links:
 * [http://www.writely.com/ writely -- the web word processor]
 * [http://www.digg.com/spy digg spy -- show console data e.g. log, recent searches, monitoring, stocks, etc]

@@ Line 130: / Line 130: @@
 == useful links ==
 [http://philip.greenspun.com/doc/ philip.greenspun.com/doc/]
 [http://philip.greenspun.com/doc/data-pipeline data-pipeline]
@@ Line 152: / Line 153: @@
 Links:
 * [http://www.writely.com/ writely -- the web word processor]
 * [http://www.digg.com/spy digg spy -- show console data e.g. log, recent searches, monitoring, stocks, etc]

← Older revision		Revision as of 16:05, 1 January 2006
Line 159:		Line 159:
	* [http://www.crockford.com/javascript/ javascript link collection]		* [http://www.crockford.com/javascript/ javascript link collection]
	* [http://en.wikipedia.org/wiki/AJAX wikipedia article on AJAX]		* [http://en.wikipedia.org/wiki/AJAX wikipedia article on AJAX]
		+	* [http://rajshekhar.net/blog/archives/85-Rasmus-30-second-AJAX-Tutorial.html 30 second intro to AJAX]

@@ Line 134: / Line 134: @@
 == AJAX/JSON support in AOLserver ==
-. HTTP request hits AOLserver, returns HTML including JavaScript with AJAX (or JSON-RPC, whatever) features.
+# HTTP request hits AOLserver, returns HTML including JavaScript with AJAX (or JSON-RPC, whatever) features.
-. Client interacts with rendered HTML application, resulting in AJAX calls to AOLserver.
+# Client interacts with rendered HTML application, resulting in AJAX calls to AOLserver.
-. AOLserver handles the AJAX calls and responds.
+# AOLserver handles the AJAX calls and responds.
-. Client potentially modified by result of AJAX call without reload.
+# Client potentially modified by result of AJAX call without reload.
 Use cases:
-. Rate something and store the rating without reload of page.
+# Rate something and store the rating without reload of page.
-. Stateful drag and drop of tiles (shopping cart, wish list).
+# Stateful drag and drop of tiles (shopping cart, wish list).
-. Background saving of application state (e.g. word processor, calendar, etc) without page reload.
+# Background saving of application state (e.g. word processor, calendar, etc) without page reload.
-. Reload portions of the view (e.g. portlet) without reloading the whole page. E.g. stock tickers, chat windows, log viewers, etc.
+# Reload portions of the view (e.g. portlet) without reloading the whole page. E.g. stock tickers, chat windows, log viewers, etc.
-. Add/remove item from cart statefully without reload of page.
+# Add/remove item from cart statefully without reload of page.
-. Recalculate shopping cart prices/totals without reload of page.
+# Recalculate shopping cart prices/totals without reload of page.
 Benefits:
-. Allows "Web 2.0" sites such as Digg and Gmail to be run on massively scalable AOLserver platform.
+# Allows "Web 2.0" sites such as Digg and Gmail to be run on massively scalable AOLserver platform.
-. It's an itch. We scratch these things.
+# It's an itch. We scratch these things.
 Links:
-[http://www.writely.com/ writely -- the web word processor]
+* [http://www.writely.com/ writely -- the web word processor]
-[http://www.digg.com/spy digg spy -- show console data e.g. log, recent searches, monitoring, stocks, etc]
+* [http://www.digg.com/spy digg spy -- show console data e.g. log, recent searches, monitoring, stocks, etc]
-[http://www.kiko.com/ kiko -- online calendar]
+* [http://www.kiko.com/ kiko -- online calendar]
-[http://mail.google.com/ google mail]
+* [http://mail.google.com/ google mail]
-[http://maps.google.com/ google maps]
+* [http://maps.google.com/ google maps]
-[http://www.crockford.com/javascript/ javascript link collection]
+* [http://www.crockford.com/javascript/ javascript link collection]
-[http://en.wikipedia.org/wiki/AJAX wikipedia article on AJAX]
+* [http://en.wikipedia.org/wiki/AJAX wikipedia article on AJAX]

← Older revision		Revision as of 22:16, 25 December 2005
Line 131:		Line 131:
	[http://philip.greenspun.com/doc/ philip.greenspun.com/doc/]		[http://philip.greenspun.com/doc/ philip.greenspun.com/doc/]
	[http://philip.greenspun.com/doc/data-pipeline data-pipeline]		[http://philip.greenspun.com/doc/data-pipeline data-pipeline]
		+
		+	== AJAX/JSON support in AOLserver ==
		+
		+	1. HTTP request hits AOLserver, returns HTML including JavaScript with AJAX (or JSON-RPC, whatever) features.
		+	2. Client interacts with rendered HTML application, resulting in AJAX calls to AOLserver.
		+	3. AOLserver handles the AJAX calls and responds.
		+	4. Client potentially modified by result of AJAX call without reload.
		+
		+	Use cases:
		+	1. Rate something and store the rating without reload of page.
		+	2. Stateful drag and drop of tiles (shopping cart, wish list).
		+	3. Background saving of application state (e.g. word processor, calendar, etc) without page reload.
		+	4. Reload portions of the view (e.g. portlet) without reloading the whole page. E.g. stock tickers, chat windows, log viewers, etc.
		+	5. Add/remove item from cart statefully without reload of page.
		+	6. Recalculate shopping cart prices/totals without reload of page.
		+
		+	Benefits:
		+	1. Allows "Web 2.0" sites such as Digg and Gmail to be run on massively scalable AOLserver platform.
		+	2. It's an itch. We scratch these things.
		+
		+	Links:
		+	[http://www.writely.com/ writely -- the web word processor]
		+	[http://www.digg.com/spy digg spy -- show console data e.g. log, recent searches, monitoring, stocks, etc]
		+	[http://www.kiko.com/ kiko -- online calendar]
		+	[http://mail.google.com/ google mail]
		+	[http://maps.google.com/ google maps]
		+	[http://www.crockford.com/javascript/ javascript link collection]
		+	[http://en.wikipedia.org/wiki/AJAX wikipedia article on AJAX]

@@ Line 13: / Line 13: @@
 # {::sha1::hmac [lindex $args 1] [lindex $args 0]}
 # config: "/security/password/query"
-# {select password, salt from users where name='[ns_dbquoteval [lindex $args 0]]'}
+# {select password, salt from users where name=[ns_dbquotevalue [lindex $args 0]]}
 # config: "/security/salt/length" "64"
 # config: "/security/salt/dictionary" "0123456789abcdefghijkl..."
@@ Line 42: / Line 42: @@
 # {lindex $args 0}
 # config: "nsz/security/password/query"
-# {select password from users where name='[ns_dbquoteval [lindex $args 0]]'}
+# {select password from users where name=[ns_dbquotevalue [lindex $args 0]]}
 </pre>

@@ Line 1: / Line 1: @@
 == towards a data and authentication layer ==
@@ Line 12: / Line 11: @@
 <pre>
 # config: "/security/password/expression"
-# {ns_sha1 [ns_md5 [lindex $args 0]] [lindex $args 1]}
+# {::sha1::hmac [lindex $args 1] [lindex $args 0]}
 # config: "/security/password/query"
 # {select password, salt from users where name='[ns_dbquoteval [lindex $args 0]]'}
-# config: "/security/salt/length" "8"
+# config: "/security/salt/length" "64"
 # config: "/security/salt/dictionary" "0123456789abcdefghijkl..."
 </pre>

← Older revision		Revision as of 20:26, 14 December 2005
Line 1:		Line 1:
−	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).
−
−	~~If you have any questions or concerns, don't hesitate to contact me. Thanks! ''-- [[User:Dossy\|Dossy]] 07:13, 3 December 2005 (EST)''~~
−
−	~~----~~
−
−	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)''
−
−	* 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)
−
−	** 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)''
−
−	*** 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)

	== towards a data and authentication layer ==		== towards a data and authentication layer ==