On Fri, Jan 28, 2011 at 17:16, Brit Butler <[email protected]> wrote: > Slobodan, > > Jeez. It's been over 3 weeks already. I'm sorry. If you look at my > tree ( http://bitbucket.com/redline6561/weblocks-dev/ or > http://github.com/redline6561/weblocks-dev/ ) you'll see that there > are a number of commits both fixing the bug with the store you noticed > and adding on to the Store API to support connection pooling which > should now be implemented in handle-client-request.
What you're saying is that you're almost finished, but need to test it to be sure? That's great news! > > What I haven't found the time to do yet is testing. I've got some > unpushed patches for a simple-demo app. So far I've compiled and run > the app but not hit it with concurrent connections, siege, etc to try > and break it. Until I've done that I'd be nervous asking for a merge > considering the changes to handle-client-request. I'm going to fix > lunch right quick and then try to get on this. I've been wanting to > get it done for a while as I intend to use it for some personal > projects as well. Testing, you say? I have about 30 MB of data in various tables and in various types that wants to be displayed, modified, created over views, forms, grids and whatnot. :-D ;-) A lot of my app-to-be will use postmodern store, so I'll do as much testing as I can with what I have. -- 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.
