PUBLIC MARKS from holyver with tag libraries

A year ago, the article Asynchronous Rendering of Portlet Content With Ajax Technology demonstrated how to apply Asynchronous JavaScript and XML (Ajax) to portlets. Since then, Ajax has become increasingly popular in the software arena and many new Ajax technologies have emerged. Examples are JavaScript libraries and toolkits, such as the Dojo Toolkit, the Yahoo! UI Library, the Google Web Toolkit, Script.aculo.us, and DHTML Goodies. In addition, new standards bodies like Open Ajax and the Dojo Foundation are key players. In light of the many developments in the past year and the host of feedback on how to use Ajax in portlets, this article describes several helpful tips and practices on how best to exploit Ajax in portlets that comply with the Java Specification Request (JSR) 168: Portlet Specification.

Stunnel is a program that allows you to encrypt arbitrary TCP connections inside SSL (Secure Sockets Layer) available on both Unix and Windows. Stunnel can allow you to secure non-SSL aware daemons and protocols (like POP, IMAP, LDAP, etc) by having Stunnel provide the encryption, requiring no changes to the daemon's code. The Stunnel source code is not a complete product -- you still require a functioning SSL library such as OpenSSL or SSLeay in order to compile stunnel. This means that stunnel can support whatever (and only) that which your SSL library can, without making any changes in the Stunnel code. The Stunnel source code is available under the GNU General Public License, meaning it is free to use in both commercial and non commercial applications as you see fit, as long as you provide source code (and any modifications) with the software. Your compiled Stunnel binary is 'restricted' by whatever license your chosen SSL library is under, however both OpenSSL and SSLeay are open source and similarly liberal in their licensing.