carmen - I'm not sure _how_ much this will really help you, but I
recently explored a similar issue with an internal Camping app.
In summary, I needed to make sure that all calls to a specific
controller were always executed serially. i.e. - if two calls came in
at approximately the same time,
hello all. ive come to the point where im thinking about deploying my 'rails on
rails' app-development solution built in camping.
mainly, im wondering what the barriers to thread-safety are.
for db, i use redland, and afaik it spawns a single db connection for each
find, and keeps a pool
2 matches
Mail list logo
