From de6ebc470f35d9c29d86fb7078cccc5bfa191613 Mon Sep 17 00:00:00 2001 From: Eric Wong Date: Mon, 16 Mar 2009 18:49:08 -0700 Subject: Start _Known Issues_ section in README Some other frameworks may also have code reloading issues. Since code reloading is mainly for development mode and Unicorn is capable of replacing the running executable without any dropping connections, broken code reloaders aren't worth fixing from our code... --- README | 11 ++++++++++- 1 file changed, 10 insertions(+), 1 deletion(-) diff --git a/README b/README index 73bb6d7..1bd0305 100644 --- a/README +++ b/README @@ -60,12 +60,21 @@ Unicorn will look for the config.ru file used by rackup in APP_ROOT. Optionally, it can use a config file specified by the --config-file/-c command-line switch. -Unicorn should be capable of running all Rack applications. Since this +Unicorn should be capable of running most Rack applications. Since this is a preforking webserver, you do not have to worry about thread-safety of your application or libraries. However, your Rack application may use threads internally (and should even be able to continue running threads after the request is complete). +== Known Issues + + * WONTFIX: code reloading with Sinatra 0.3.2 (and likely older + versions) apps is broken. Since this is no longer an issue with + Sinatra 0.9.x apps and only affected non-production instances, this + will not be fixed on our end. Also remember we're capable of + replacing the running binary without dropping any connections + regardless of framework :) + == Contact Newsgroup and mailing list coming, or it'll be a part of the Mongrel project... -- cgit v1.2.3-24-ge0c7