gmane.lisp.web

The Common Lisp Directory finally crashed after 823 days.

Marc Battyani — 2008-03-15T17:05:40

[Is this list still somewhat alive?] The Common Lisp Directory (http://www.cl-user.net) lisp process crashed yesterday after 823 days of continuous service. In these 2 years and 93 days, the same lisp process (LispWorks on Linux Debian) served 273M requests without any problem. Even the crash was not really lisp's fault as it was caused by a swap disk problem which caused the kernel to kill a lot of processes. During these 823 days, I had to restart Apache every few months and the firewall router every several days. I also got several electric power outages but fortunately none longer than the 3h of UPS battery time. BTW this shows than Debian is also a stable platform for this kind of applications. So the CLD lisp process uptime experiment is now over and I will move the CLD to a better place than a simple server in my basement. Marc

serving very large files from allegroserve

Nick Levine — 2007-05-03T09:00:31

Testing downloads of large audio recordings from ilc2007, I find that the bytes stop flowing after five minutes. Allegroserve (version 1.2.43 on ACL 8.0) spits out a 500 return code and the transaction is over. I find in AServe doc the following: (wserver-response-timeout wserver) - the number of seconds AllegroServe allows for an http request function to be run and finished sending back its response. The initial value for this slot of the wserver object is found in *http-response-timeout* which defaults to 300 seconds. You can alter this timeout value with the :timeout argument to with-http-response or by specifying a :timeout argument to the publish function creating the entity. and I'm sure this is exactly what I've hit. The thought of just cranking this number up and hoping for the best makes me cringe a little. Surely there must be better? Well, the folks at Franz obviously thought so too, because a couple of paragraphs up they say: In Acl 6.1 we added the capability of having each I/O operation to a socket stream time out. This means that we don't have to predict how long it should take to get a request or send a response. As long as we're making progress reading or writing we know that the client on the other end of the network connection is alive and well. Fine words. But totally contradicted by having a response-timeout slot in the server. Does anyone have any experience with getting AServe to monitor whether it's "making progress reading" and so knows "that the client on the other end of the network connection is alive and well"? Thanks, - nick

Announcement: CL-WEBDAV

Edi Weitz — 2007-04-18T20:14:50

A WebDAV server based on Hunchentoot: http://weitz.de/cl-webdav/ Cheers, Edi.

web development with lisp

Patrick X — 2007-03-16T04:46:38

Hey this is Patrick, from Pippen Enterprises LLC. Our company is starting up a web development company, using Common Lisp of course :-) We wondering what tools do many lisp developers, use that support Versign SSL, and other technologies for commercial use.

Araneida: request-authorized-p (implementation of genericfunctionto yield authorization status)

Joubert Nel — 2007-03-06T03:53:50

Hi, I'm trying to create an authorization scheme in Araneida. Basically whenever a location in my URL space is called I want to check whether the user is authorized and redirect to a login page if he isn't. I found this post on usenet: http://groups.google.com/group/comp.lang.lisp/browse_thread/thread/a6990567666934d2/12bca167849b64e9?lnk=gst&q=request-authorized-p&rnum=1&hl=en&fwc=2 According to this post, the generic function "request-authorized-p" is called for every request to determine whether a client is authorized. To test this, I've got: ============= snip ================== (defclass root-page-handler (araneida:handler) ()) (defmethod request-authorized-p ((araneida:handler root-page-handler) method request) (format t "not authorized")) (defmethod request-not-authorized ((araneida:handler root-page-handler) method request) (araneida:request-redirect request *login-urlstring*)) (defmethod handle-request-response ((araneida:handler root-page-handler) method request) (araneida:request-send-headers request) (araneida:html-stream (araneida:request-stream request) `(html (body (p "logged in"))))) (defparameter *root-page-handler-instance* (make-instance 'root-page-handler)) (araneida:install-handler (http-listener-handler *listener*) *root-page-handler-instance* *app-urlstring* t) ============= snip ================== So, I've got request-authorized-p on class root-page-handler. However, I find that this method is never called by Araneida; instead, handle-request-response is still called. What gives? What am I missing? Joubert

problems installing lisp on xen vps on amd64 machine

Naveen Garg — 2007-02-25T07:55:07

_______________________________________________ lispweb mailing list lispweb< at >red-bean.com http://www.red-bean.com/mailman/listinfo/lispweb

[ANN] cl-migrations 0.0.1

Vamsee Kanakala — 2006-11-12T03:43:12

Hi all, I would like to announce the availability of cl-migrations, a port of the migrations feature of Ruby on Rails to Common Lisp. cl-migrations is a simple tool to manage your changes to a database as you develop your web application or any database-backed application. It works by generating a new file to for each database change, which contains the DDL required to enable and disable that change. So, effectively you can version-control your entire database structure. You can install this tool with asdf: (asdf-install:install :cl-migrations) This tool depends on clsql, so you can run migrations on any database that is supported by clsql. Many thanks to Kevin Rosenberg for maintaining such a useful library. For more info, please go to this page: http://common-lisp.net/project/cl-migrations/ Kindly raise any questions/feature requests/bug-reports here: http://common-lisp.net/cgi-bin/mailman/listinfo/cl-migrations-devel Regards, Vamsee Kanakala.

Hello

George Erick Tasso — 2006-10-23T00:05:53

_______________________________________________ lispweb mailing list lispweb< at >red-bean.com http://www.red-bean.com/mailman/listinfo/lispweb

Hello

George Erick Tasso — 2006-10-23T00:05:53

_______________________________________________ lispweb mailing list lispweb< at >red-bean.com http://www.red-bean.com/mailman/listinfo/lispweb

How does reverse proxy helps araneida?

Anton Vodonosov — 2006-10-20T23:57:13

I do not understand. "Araneida ... designed to sit behind proxying Apache ... ". What for? How does Apache helps (without regard for https)? Explain it me, someone, please. Regards, -Anton

How does reverse proxy helps araneida?

Anton Vodonosov — 2006-10-20T23:57:13

I do not understand. "Araneida ... designed to sit behind proxying Apache ... ". What for? How does Apache helps (without regard for https)? Explain it me, someone, please. Regards, -Anton

Redirects and caching

Jonathon McKitrick — 2006-10-20T01:16:37

Suppose you have a page that requires cookie-based authentication, and that redirects when that cookie is not found. How do you make sure neither page is incorrectly cached? Right now, I am able to access a cached page after the cookie has been removed. Worse, after accessing a protected page, being redirected, then logging in and going *back* to that page, I am still getting the redirect. Is there a way around this? I have "no-store, no-cache" in the cache-control headers. Jonathon McKitrick -- My other computer is your Windows box.

Redirects and caching

Jonathon McKitrick — 2006-10-20T01:16:37

Unclosed file descriptors

Jonathon McKitrick — 2006-10-11T16:50:57

Is it any reason to worry about 'unable to close fd 6' and 'trying harder'? Jonathon McKitrick -- My other computer is your Windows box.

Unclosed file descriptors

Jonathon McKitrick — 2006-10-11T16:50:57

Is it any reason to worry about 'unable to close fd 6' and 'trying harder'? Jonathon McKitrick -- My other computer is your Windows box.

extending Allegroserve time-out period

Lawrence Au — 2006-10-10T23:23:15

I've got a slow back end executable producing new files that I need to serve, and it takes about 20 to 45 seconds for it to complete. Meanwhile, my PortableAserve thread times out and I get a NET.ASERVE::STREAM-ERROR-IDENTIFIER error in the aserve-worker thread. Is there a way to extend the time-out period to 45 seconds? I'm using PortableAserve on Lispworks. Lawrence Au Q-Phrase LLC

extending Allegroserve time-out period

Lawrence Au — 2006-10-10T23:23:15

Announcement: Drakma

Edi Weitz — 2006-10-10T19:53:02

While I'm at it, I should probably also mention Drakma which I think I haven't announced on this list yet. Drakma is a fully-featured web client (implemented in Common Lisp, obviously) that knows how to handle HTTP/1.1 chunking, persistent connections, re-usable sockets, SSL, continuable uploads, file uploads, cookies, and other things. It is known to work with LispWorks, AllegroCL, CMUCL, SBCL, and OpenMCL. I /think/ it will also work with CLISP and ABCL, but I haven't tested. More info here: http://weitz.de/drakma/ OK, enough advertising for tonight - back to our regular scheduled program...

Announcement: Drakma

Edi Weitz — 2006-10-10T19:53:02

Announcement: Hunchentoot

Edi Weitz — 2006-10-10T19:16:59

Hi! I'd like to announce that Hunchentoot has now been ported to SBCL, CMUCL, AllegroCL, and OpenMCL. Hunchentoot is a fully-featured web server written in Common Lisp which can be operated stand-alone but also as a back-end for mod_lisp. Hunchentoot was previously only available for LispWorks, as a wrapper around TBNL. The latest version doesn't depend on TBNL anymore and is intended to replace it. More information about Hunchentoot is here: http://weitz.de/hunchentoot/ Cheers, Edi.

Announcement: Hunchentoot

Edi Weitz — 2006-10-10T19:16:59