And the client accessed it using the first URL. Then the server would know
and give the appropriate response (for example notified a newer version of
the client apps).
I don't have any code at the moment, since I'm just planning to implement
it. I know that if I use ActionLink i can do this, the protocol_version
would just be another parameter in the onActionFromXXX method. But that
means i would have to write the same code for each of the method that is
accessed by the mobile client. I'm wondering if i could do this only in one
place. I hope my intention is clear enough.
The philosophy in Tapestry is that action links are transient ...
their value is dependent on the exact structure of the page which can
change between deployments ... and that's OK because component event
links (ActionLink is a specific application of a component event
request) are NOT bookmarkable; because of Tapestry's
redirect-after-event strategy, the only URLs that a user will see in
the browser's URL field will be a page render request URLs, and
Tapestry has facilities (generally, advanced usage of the activate and
passivate events) to keep those stable even when underlying
implementation of the pages evolve.