The OpenAPI project mentioned in an earlier blog entry has now been renamed to OpenResty because there's hundreds of thousands of things that call themselves OpenAPI or so, which can be really confusing ;)

But for backward-compatibility, I didn't change the name of the Subversion repository. So it's still located at http://svn.openfoundry.org/openapi/trunk.

I've put OpenResty as well as its dependency modules onto CPAN to help people play with it. A third (fake) backend, PgMocked, was added just recently to make CPAN testers' life easier.

The documentation still needs love very badly. The work on the English spec for OpenResty's REST interface has started in the form of OpenResty::Spec::REST and I need to translate most of the stuff in its Chinese version over here. And you may find the `` cheat sheet '' interesting too ;)

In the days of the Chinese New Year, I built a personal blog site using OpenResty's JavaScript client libary , Jemplate , and Audrey's Pugs blog's page templates:

http://blog.agentzh.org

It's a very fast site at least here in China and the hand-written JavaScript code for this site is remarkably clean (just around 300 lines):

http://blog.agentzh.org/blog.js

Due to the lack of RSS and email-to-blog support in OpenResty today, I'll still have to use the (slow) live.com space as my main blog site for a while.

Also carrie++ in our team has updated our Yisou BBS, taking advantage of OpenResty 's Chinese captcha support:

http://www.yisou.com/opi/post.html

English captchas are also supported and I'm pondering using this feature in my new blog site too.

It's worth mentioning that the deployment of these pure AJAX sites is 0 because they're just a set of static files ;) The complexity all goes to the OpenResty server . The web services provided by an OpenResty server is completely general-purpose and also scriptable by users (via the minisql language). That's the beauty of this open architecture :)

Client library in Perl for OpenResty, WWW::OpenResty, is also on CPAN. It's just a thin wrapper around LWP::UserAgent. In fact, most of the client-side operations can be done in a plain web browser's address bar ;) And yeah, special care should be taken while using GET for writing/deleting operations for the sake of XSS attacks. Cookies for sessions are now disabled by default in OpenResty (thanks Eidolos++'s reminding).

Both my $boss and I love to see OpenResty's REST design becomes a part of Jifty or let OpenResty be a funny component in Jifty or some other web application frameworks (as virtual models, for example) in the future. And Eidolos++ on #jifty has already shown great interest in OpenResty's API after taking a peek at its test suite .

I'll mostly focus on the documentation for all these cool stuffs in the coming weeks. Stay tuned!