On Sun, Jan 31, 2010 at 9:11 PM, HS WAI drwa...@yahoo.com.sg wrote:
Hi,
Thanks for your prompt response.
I want to get the value form user input/selected option
html
body
select name='query' id='query'
option value='a'a/option
option value='b'b/option
/select
%
# How to get
Hi,
I don't recall if I've already submitted this enhancement...
I've written a memcached based Session that others might find useful. Feel
free to use as you wish.
Usage:
1. Name the file SessionMemcachedStore.py in WebKit directory
2. Configure your Application.config:
SessionStore =
On Sun, Apr 11, 2010 at 4:23 PM, Christoph Zwerschke c...@online.de wrote:
Am 15.03.2010 19:38 schrieb Steve Schwarz:
I've written a memcached based Session that others might find useful.
Feel free to use as you wish.
I had some time today to try it out. Works nicely. I have added some
On Sun, Apr 11, 2010 at 4:32 PM, Steve Schwarz st...@agilitynerd.comwrote:
On Sun, Apr 11, 2010 at 4:23 PM, Christoph Zwerschke c...@online.dewrote:
Am 15.03.2010 19:38 schrieb Steve Schwarz:
I've written a memcached based Session that others might find useful.
Feel free to use as you wish
Hi,
We are looking to run multiple Webware instances from a single Webware
directory/checkout and can do so by providing configuration differences via
command line args. But I noticed that ThreadedAppServer.addSocketHandler()
creates files like http.address and adapter.address containing the
On Tue, Jun 8, 2010 at 2:35 PM, Christoph Zwerschke c...@online.de wrote:
Am 08.06.2010 21:27 schrieb Steve Schwarz:
We'd like to simplify our deployment. Now our admins have to install
Webware multiple times for each appserver instance on multiple servers.
It would be easier to just
On Tue, Jun 8, 2010 at 3:56 PM, Christoph Zwerschke c...@online.de wrote:
Maybe a MultiProcessAppServer could be the alternative or somethin with
an approach like Concurrence or Twisted.
We are using Twisted to dispatch/maintain the Webware process pool. Will see
about possibility of open
Hi,
We ran across an interesting problem with sessions being automatically saved
by Transaction.py. We had a situation where two AJAX requests were issued
and one of the requests updates the session and it started and completed
within the lifetime of another request. In that scenario the
On Thu, Mar 3, 2011 at 9:28 AM, Christoph Zwerschke c...@online.de wrote:
IMHO the most simple solution would be to keep a dirty flag (set
whenever __setitem__ or __delitem__ is called for the session) and then
save the session only when the dirty flag has been set. This will also
be good for
On Thu, Mar 3, 2011 at 2:23 PM, Christoph Zwerschke c...@online.de wrote:
Btw, which kind of session store are you using? The default DynamicStore
is based on the MemoryStore, and here requests share the same session
object. So the scenario you described should actually not cause a
problem
10 matches
Mail list logo
