W dniu 04.02.2013 17:53, C Anthony Risinger pisze:
On Mon, Feb 4, 2013 at 9:56 AM, Łukasz Mach <[email protected]> wrote:
W dniu 09.11.2012 14:17, Łukasz Mach pisze:
Hi,
Today I ecountered following problem: I made change in pyjamas code,
compiled it with pyjsbuild, uploaded to server.
In effect, some of users had partially updated code, eg. one .js files
was downloaded from server, with recent body, and other - from cache,
with outdated body.
Obviously, such partially upgraded application didn't work properly and
I have lot of whinning that "doesn't work". I had to instruct everyone
to press ctrl-shift-r or ctrl-f5.
I faced the problem first time, however it looks like quite standard
one, so probably some of you had it and probably solved somehow.
So, how do you handle problem with versions of pyjs code?
I'm not sure if it's important, but my case is existing webpage with
<script src="bootstrap.js"></script> addon.
Am I only one who face such problem when doing pyjs apps? Don't we have some
kind of standard solution?
have you tried --enable-signatures? this may only be effective if you
are also using --dynamic-link, but it appends the md5 hash of the
input python file to the name of the javascript output file... thus
when stuff changes the sig changes too.
there are still a couple edge cases that need to be fixed eventually,
but it should do what you need as-is.
Thanks, I didn't know about that option. Looks like it's what I was
looking for.
--
pozdrawiam
Łukasz Mach - [email protected]
--
---
You received this message because you are subscribed to the Google Groups "Pyjs.org Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
