On Wed, Apr 4, 2012 at 4:12 PM, Metacraft <[email protected]> wrote: > I need to know the current status of weblocks + clsql status as of > March/April 2012 with respect to fluid/multi-threading? >
I am using Weblocks and CLSQL in an app that is... well, not quite in production use yet, but will be in a few weeks. I haven't tried the demo in a long time, and don't recall what state it's in, but my app seems to be working fine. There are some useful patches in my public Weblocks repo, which I don't think have been merged into the official one yet. Take a look: https://github.com/slburson/weblocks > I have read about all of the dozens of the forum articles and page > that I could search on this topic. But there is no clear conclusion > (the discussion about clsql vs fluid regarding thread safety is one or > two years old). Then there are recommendations from CLSQL site about > not using fluid. Is there a version of weblocks mysql store that is > thread-safe and works (with or without fluid)? > I've only tested my app under light load yet, but as far as I can tell, it is thread-safe (I am using CLSQL-Fluid). It definitely was not thread-safe when I was not using CLSQL-Fluid -- I thought I had an alternative approach that would work, but it didn't. I definitely recommend using CLSQL-Fluid. I think the objections to it are mistaken. Oh, I am using Postgres rather than MySQL, so I can't be so sure the latter works, but I don't know any reason it wouldn't. -- Scott -- You received this message because you are subscribed to the Google Groups "weblocks" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/weblocks?hl=en.
