Bob,
Tapestry itself will not yell at you for not setting the version
number.
However, as Josh indicated the auto-generated version number doesn't
work well in a clustered environment, beyond "just generating extra
requests". For example, in the past when I've deployed my app to GAE w/o
explicit version numbers I'd run into an issue with an intermittent loss of
style, the issue goes like this:
* A request comes into GAE for my app
* GAE spins up a new instance of the app to handle the request. This
generates app version 1.
* Inside of the page served by app version 1, there are a bunch of tapestry
assets that include the app version in the URL. The browser makes additional
requests for those assets (e.g. /appName/assets/1/foo.jpg)
* GAE receives requests for assets but decides to spin up a few more
instances of the app, thus generating app version 2. App version 2 receives
requests for assets from app version 1 and balks - it doesn't have the
assets being asked (e.g. /appName/assets/1/foo.jpg), rather it has (e.g.
/appName/assets/2/foo.jpg). It sends a "not found response".
* The page being rendered by app version 1 shows up broken - it couldn't
pick up a few of the images or stylesheets it needed.
Cheers,
Alex K
On Wed, Jan 19, 2011 at 9:51 PM, Bob Harner <[email protected]> wrote:
> Understood, but what I was really trying to ask is whether Tapestry
> now (as of 5.2) in some way "forces" you to set the application
> version number (or yells when you don't) or whether -- as I'm assuming
> -- byou'll just generate unnecessary extra requests to the app because
> of the URLs changing.
>
> On Wed, Jan 19, 2011 at 9:30 PM, Josh Canfield <[email protected]>
> wrote:
> > The default gives a new url every time you start the server, and on every
> > server in the cluster. It really only works in a dev environment.
> > On Jan 19, 2011 5:54 PM, "Bob Harner" <[email protected]> wrote:
> >> Hi everybody,
> >>
> >> I was reviewing/updating the Confluence-based documentation and have a
> >> question. The 5.2.0 release notes say:
> >>
> >> "It is now quite necessary to configure the application version
> >> number: all assets are exposed via a URL that incorporates the
> >> application version number; in previous releases, each library could
> >> configure its own version number. By implication, changing library
> >> versions and nothing else will now require a change to the application
> >> version number."
> >>
> >> I understand the part about the application version number now
> >> affecting library-based assets, but strictly speaking is it really
> >> mandatory to set the application version number now? Or just very
> >> highly recommended?
> >>
> >> As far as I can tell in the code, Tapestry will still generate a
> >> random application version number for you:
> >>
> >> configuration.add(SymbolConstants.APPLICATION_VERSION,
> >> Long.toHexString(random.nextLong()));
> >>
> >> My intent is to make the documentation consistent, which it isn't yet.
> >>
> >> Thanks!
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: [email protected]
> >> For additional commands, e-mail: [email protected]
> >>
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>
