Yes, I've seen many workarounds in this group.
But I just want to point this issue again because I think GAE needs a
good "web_dev_server" :)
Regards
Sylvain
On 13 sep, 11:56, "Barry Hunter" <[EMAIL PROTECTED]> wrote:
> Many developers on here have reported success with a caching proxy
> sitt
We use Apache to serve up all static content in development mode, and
dev_appserver for everything else. A build script updates a path
variable that the html templates use to fetch the static content, so
that static content is served by GAE.
On Sep 13, 6:14 am, Sylvain <[EMAIL PROTECTED]> wrote:
By the way, an optimization would be to put all those images in one
image file, and use background offsets and div sizes in CSS to control
the viewport (I believe this technique is called "spriting"). Gmail
does just that:
http://mail.google.com/mail/images/2/5/c/icons1c.png
This will reduce the
Have you tried the new 1.1.3 SDK? Serving static files from
dev_appserver feels generally faster and it supports basic
browser-side caching now ("Expires" + "Cache-Control").
Karsten
On Sat, Sep 13, 2008 at 11:14, Sylvain <[EMAIL PROTECTED]> wrote:
>
> Yes, I've seen many workarounds in this g
Yes, with 1.1.3 with caching, it is much better.
Regards
On 16 sep, 19:29, "Karsten Petersen" <[EMAIL PROTECTED]>
wrote:
> Have you tried the new 1.1.3 SDK? Serving static files from
> dev_appserver feels generally faster and it supports basic
> browser-side caching now ("Expires" + "Cache-Con
