Thank you Anthony, I knew session.forget() but did not know it would
be so helpful for performance. I'll try that in my projects from now
on.
Regards,
Ray
On Aug 26, 2:42 am, Anthony wrote:
> If you don't explicitly "forget" the session, the session file will lock on
> each request, so subsequen
On Thursday, August 25, 2011 3:28:38 PM UTC-4, G wrote:
>
> Hi,
> Can you explain this a bit more? Is the idea to call
> session.forget(response) in my main controller, but not in the
> components that have forms in them? I had previously put the
> session.forget() line in the model file so it
Hi,
Can you explain this a bit more? Is the idea to call
session.forget(response) in my main controller, but not in the
components that have forms in them? I had previously put the
session.forget() line in the model file so it was always executed.
Thanks
On Aug 25, 11:42 am, Anthony wrote:
> If y
If you don't explicitly "forget" the session, the session file will lock on
each request, so subsequent requests will be blocked. Maybe you could forget
the session on requests that don't need it and just keep it for requests
that do need it (i.e., form submissions).
Note, to immediately unlock
I tried session.forget() but found that forms submitted by ajax in
components don't seem to work without a session, so that won't work in
my case.
I also tried removing the SQLite db, it may have helped some but I'm
still testing.
Thanks again for the suggestions
On Aug 24, 4:18 pm, Michele Comi
Hi G,
I saw similar behaviors in some of my lightweight app, which also uses
sqlite and rocket. I need not solve that problem at that time (it was
really a little app for a small group). But I can provide some
information to you this time.
When you try to isolate the sqlite, "using no auth and ra
Try session.forget() and see what happens
mic
2011/8/25 G :
> Thank you for the suggestion. I made a test application that used no
> database accesses (no auth and randomly generated data). It showed the
> same behavior, so I do not think it is the culprit. In addition, since
> the application i
Thank you for the suggestion. I made a test application that used no
database accesses (no auth and randomly generated data). It showed the
same behavior, so I do not think it is the culprit. In addition, since
the application is monitor only, the real application only reads from
the database, whic
You also need to consider the database type used by the application for the
model. The SQLite database has a transaction lock which will cause the
application to look like it is single threaded if the database is held in a
transaction pending state while the background work is performed.
I should also mention I'm open to other suggestions to alleviate this
problem. The end goal is to display information (text or image) then
request an update, and when it's ready, display the new text/
information.
G
On Aug 24, 11:39 am, G wrote:
> Hi,
> First a little background: My application
10 matches
Mail list logo
