http://textpattern.com/?v=4.6.2SpicyNoodles!http://www.spicynoodles.net/
Sun, 08 Apr 2018 08:48:08 GMTMoving out
Welcome to my new home on the web!

After hosting my humble website with a local company for more than four years, I have decided to move to a new hosting provider who offers a lot more features and consequently a lot more exciting opportunities for me to screw things up.

In a couple of days, spicynoodles.net should resolve to this website too and all old links will hopefully keep working, including the URL for my RSS feed. If you stumble across any broken links, please let me know.

Who knows, maybe I will even get around to updating this site a little more often than during the last few years.

]]>
http://www.spicynoodles.net/article/20051008
Sat, 08 Oct 2005 15:00:00 GMTAndré Radketag:www.spicynoodles.net,2005-10-08:833a7e06fa197ec6d4eeb4b65dd270da/f668c92baad3cd15d2d2bc5b95b8b314September 28th, 2004
So it begins...]]>
http://www.spicynoodles.net/article/20040928
Tue, 28 Sep 2004 10:14:00 GMTAndré Radketag:www.spicynoodles.net,2005-09-23:833a7e06fa197ec6d4eeb4b65dd270da/b0720761c2f8e8736643cf65c094fb8cNovember 5th, 2002
Over the last few months, I noticed a few requests for an XSLT processor that would run in Frontier and Radio. After experimenting with both the Apache XML project’s Xerces / Xalan and the Gnome project’s libxml / libxslt libraries, I finally managed to produce a working extension for Frontier and Radio based on the Ginger Alliance’s Sablotron:

To install, unpack the archive and open the resulting file with Frontier or Radio.

Please note: This release is for thrill seekers only. It is neither feature-complete nor fully debugged. I have done some light testing on Mac OS X and Windows 2000, but the Mac OS Classic version has not been tested at all. If this release blows up your machine, I will not accept any responsibility.

The DLLs shipping with this release log a lot of internal information to a text file named “sablotron_dbg_log.txt” that might end up in your Frontier or Radio folder or whatever happens to be the current working directory.

The processor currently ignores any encoding specified in the stylesheet for the output document as Sablotron only supports UTF-8 natively for output. Support for other common encodings will of course be added later.

There is only minimal documentation in the form of a sample script at sablot.examples.transformTest.

Finally, it is entirely possible that there will be some fundamental changes to the API over the next few releases that will break all scripts written to the current API. You have been warned.

That said, I am very interested in any kind of feedback from anyone who dares to experiment with this release.

Since the last public release, I fixed a bug in the Mac OS X networking code that would block all Frontier threads while the extension was waiting for a response from the server after submitting a query for execution.

As a side effect of the fix, it is now possible to abort calls into the verbs for executing queries and retrieving multiple/all rows of a result set via the usual cmd/ctrl-period mechanism (or the Kill button of a script window). This will send a request to the server asking it to cancel the current query and close the network connection cleanly, but it will not deallocate all resources associated with the connection on the client side.

This update is strongly recommended for anyone using the extension on Mac OS X. While the original blocking behavior only manifested itself on Mac OS X, the ability to kill queries was also implemted for the Mac OS Classic and Windows versions.

The only change since 1.0a10 consists of a fix for an infinite loop bug in the connection pooling logic. Once the time specified by the restartTimeoutSecs parameter of the postgreSQL.pool.create verb had run out, the extension would continuously close and re-open a connection to the database server.

This update is strongly recommended for anyone using the connection pooling feature of the extension.