relevance / castronaut

writing tests & specs for concurrency is seldom practical, so I am not sure what the current expectation is wrt CAStronaut & concurrency. However, it seems that support for concurrency is nominal right now. I think for starters we need to develop:

1. a concurrency benchmark (in lieu of a spec)
   
2. a recipe for clustering CAStronaut server instances
   
3. a means for improving concurrency in CAStronaut itself (connection pools, multithreading and the like)

original LH ticket

This ticket has 0 attachment(s).

spec/app/controllers/db/ and spec/app/controllers/log/ should be removed from the gemspec. From the looks of it, there may be some other graft that could be removed as well.

original LH ticket

This ticket has 0 attachment(s).

Now that FF3 can support HttpOnly along w/ IE, HttpOnly cookie support makes sense as a security improvement. Rails also uses this as default.

https://rails.lighthouseapp.com/projects/8994/tickets/1046

This is probably an issue for rack as well, and perhaps that is the proper place to address this? I will post a ticket there as well.

original LH ticket

This ticket has 0 attachment(s).

try to login as and observe error message.

original LH ticket

This ticket has 0 attachment(s).