Re: Optional separation of the concepts of how long server caches content and how long it tells client to cache it

2014-12-30 Thread Alejandro Dubrovsky
On Monday, December 29, 2014 2:01:28 PM UTC+11, Carl Meyer wrote: > > Hi Alejandro and Russell, > > On 12/28/2014 07:29 PM, Russell Keith-Magee wrote: > > On Sun, Dec 28, 2014 at 8:13 PM, Alejandro Dubrovsky > > > wrote: > >> On Sunday, December 2

Re: Optional separation of the concepts of how long server caches content and how long it tells client to cache it

2014-12-28 Thread Alejandro Dubrovsky
On Sunday, December 28, 2014 7:23:34 PM UTC+11, Alejandro Dubrovsky wrote: > > > On Sunday, December 28, 2014 1:03:26 PM UTC+11, Russell Keith-Magee wrote: >> >> >> On Sat, Dec 27, 2014 at 9:30 PM, Alejandro Dubrovsky >> wrote: >>> >>> Hi all

Re: Optional separation of the concepts of how long server caches content and how long it tells client to cache it

2014-12-28 Thread Alejandro Dubrovsky
On Sunday, December 28, 2014 1:03:26 PM UTC+11, Russell Keith-Magee wrote: > > > On Sat, Dec 27, 2014 at 9:30 PM, Alejandro Dubrovsky > wrote: >> >> Hi all, >> >> When running a small, low traffic site on slow cloud servers (eg >> DigitalOcean), it&

Optional separation of the concepts of how long server caches content and how long it tells client to cache it

2014-12-27 Thread Alejandro Dubrovsky
Hi all, When running a small, low traffic site on slow cloud servers (eg DigitalOcean), it'd be useful to be able to cache pages, not because the site might be taken down from too many request, but to improve responsiveness. A non-trivial page that might take a few hundredth of a second to ser

Re: Use case for #14914 (to_db_python)

2013-08-08 Thread Alejandro Dubrovsky
On Wednesday, August 7, 2013 5:22:29 PM UTC+10, Anssi Kääriäinen wrote: > > On Monday, August 5, 2013 8:02:52 AM UTC+3, Jani Tiainen wrote: >> >> Hi, >> >> You seem to found kind of an issue which happens with GeoDjango part as >> well. Most of the geodjango operations require quite heavy to/fr

Re: Use case for #14914 (to_db_python)

2013-08-08 Thread Alejandro Dubrovsky
take a look how > different GeoDjango backends deal with the similiar problem. > > On Thu, 1 Aug 2013 21:23:40 -0700 (PDT) > Alejandro Dubrovsky > wrote: > > > Looking around for a way to get the connection on deserialisation, I ran > > into #14914 <https://code.dj

Use case for #14914 (to_db_python)

2013-08-02 Thread Alejandro Dubrovsky
Looking around for a way to get the connection on deserialisation, I ran into #14914 which was closed wontfix 3 years ago with a request for a use case for the change. Here is my use case: I'm writing an encrypted char field, with encryption happeni