= Blisted.org =

This is just a place where [wiki:AboutMe I] stuff my stuff, keep my
[http://www.blisted.org/blog blog], [http://www.blisted.org/browse code], and 
other things.

== [wiki:papers Papers] ==
 * [wiki:papers/concepts/services/aggregation Webservice Aggregation for Document Generation]
 * [wiki:papers/opinions/JavaScript2.0 My point of view on JavaScript 2]
 * [wiki:papers/opinions/JavaScriptPackages Giving JavaScript Packages]
 * [wiki:papers/talk/XMLMVC Client side MVCs in web applications]
 * [wiki:papers/tutorials/c/100lines/MemoryPools 100 lines or less: Memory pools in C]
 * [wiki:papers/tutorials/java/100lines/UlteriorClassLoader 100 lines or less:  Test Re-factoring with Multiple Class Loaders]
 * [wiki:papers/tutorials/java/100lines/FastCircularBuffer 100 lines or less: Fast circular buffers]
 * [wiki:tutorials/setup/gprs GPRS EDGE and the Samsung t519 in Ubuntu Linux]

== [wiki:projects Projects] ==
 * [wiki:projects/CuIRC A curious perl IRC client]
   ''(dead)''
 * [wiki:projects/IMS The dusty, still useful Image Manipulation Spider]
   ''(available)''
 * [wiki:projects/JianCha My latest all-spec, no-code code review system]
   ''(active)''
 * [wiki:projects/awkbot A 100% GNU AWK IRC Bot]
   ''(available)''
 * [wiki:projects/sagot A new programming environment for Javascript]
   ''(active - incomplete)''

== Libraries ==
__'''Perl'''__
 * [http://search.cpan.org/~tag/POE-Component-Client-TCPMulti-0.0521/lib/POE/Component/Client/TCPMulti.pod POE::Component::Client::TCPMulti] 
   A high performance [http://poe.perl.org/ POE] Component optimized for High 
   Connectivity and easy migration from POE::Component::Client::TCP. As opposed 
   to the ::Client::TCP Component, this module maintains all concurrent 
   connections in a single POE::Session, which greately reduces overhead. Many 
   other optimizations have been considered, and other functionality has been 
   added as well (Such as being able to change each inh2idual connections Filter 
   dynamically). Available on [http://search.cpan.org/ CPAN].
 * [http://search.cpan.org/~tag/POE-Component-Pool-Thread-0.013/Thread.pm POE::Component::Pool::Thread] 
   A [http://poe.perl.org/ POE] component for a boss/worker thread pool, the boss 
   thread being a 
   [http://search.cpan.org/~rcaputo/POE-0.9917/lib/POE/Session.pm POE Session] 
   Allows you to use non-cooperative code from within a cooperative environment,
   and easily share data.
 * [http://search.cpan.org/~tag/Curses-UI-POE-0.02801/POE.pm Curses::UI::POE]
   Curses::UI::POE is a small perl module that forces the Curses::UI toolkit to 
   the [http://poe.perl.org/ POE] event based framework for all of its I/O 
   handling. This makes Curses::UI multitasking-ready hot off the platter, and 
   allows you to mix and match it with various POE Components to make very nice 
   console networking (and other) applications.
__'''JavaScript'''__

 * [source:/trunk/cookie.js cookie.js]
   A library for reading and writing multi-value cookies similar to those written
   by [http://search.cpan.org/author/LDS/CGI.pm-3.27/CGI/Cookie.pm CGI::Cookie]
   and [http://search.cpan.org/author/STAS/libapreq-1.33/Cookie/Cookie.pm Apache::Cookie].
 * [source:/trunk/hierarchy.js hierarchy.js]
   A library for building hierarchal menus with JavaScript.
 * [source:/trunk/Properties.js Properties.js]
   A set of objects designed for parsing Java properties files in JavaScript.
   Supports a subset of the properties file format, and completely supports
   the XML properties format.

__'''AWK'''__

My AWK projects lack real documentation, partially because there isn't any
particularly good way to document AWK.  Most of them a part of the afore mentioned
awkbot.
 * [source:trunk/awkbot/lib/mysql.awk mysql.awk]
   A library for talking to mysql through coprocessing /usr/bin/mysql
   ''gawk only''
 * [source:trunk/awkbot/lib/irc.awk irc.awk]
   Actually a bit of a framework for building IRC Clients in awk, although I can't
   see it having a great amount of use, it is reusable.  It works by letting you
   callbacks for many protocol actions, if the callback is registered, the
   appropriate function is called (blindly, assuming it's there).
   Only supports a small subset of the protocol.

...There are more available only in my repository, and even more scattered around
my filesystem which I've yet to check in or remember.