On 6/28/07, Doug B <[EMAIL PROTECTED]> wrote:
>
> Are you sure the request is actually being made, and not ignored by
> the browser? If you do GETs to the same url with the same parameters
If you do requests that have side effects, you shouldn't be using GET.
Consider POST.
--~--~-~--~
Are you sure the request is actually being made, and not ignored by
the browser? If you do GETs to the same url with the same parameters
(your boolean I assume) the browser will simply ignore the request. I
ran into that trying to do some ajax stuff, and ended up appending a
timestamp number as
Specifically, the boolean values describe certain types of data the
user wishes to mask when looking through the database. The values are
specific to each user, so there is no reason to DB them. I am storing
them in the session variable. The problem is that the variables are
not updated instant
On 6/27/07, Val <[EMAIL PROTECTED]> wrote:
>
> Specifically, the boolean values describe certain types of data the
> user wishes to mask when looking through the database. The values are
> specific to each user, so there is no reason to DB them. I am storing
> them in the session variable.
The
On 6/27/07, Val <[EMAIL PROTECTED]> wrote:
...
>change a boolean
> value
A boolean value where, in what context, for what purpose?
> it
> takes multiple refreshes for the value to update itself.
There are multiple processes in general-- runserver is one process,
but shouldn't be used outside of
I am having difficulty with re-rendering the same template. My site
is designed with links which, when clicked, will change a boolean
value (this is done via a query string), then re-render the page they
were clicked from. The problem is that when the page is rendered, it
takes multiple refreshe
6 matches
Mail list logo
