Hi, I have looked into it, somewhat, for some non-standard page generation. The first number is the context id, which increases with each page viewed in a session. The rest is the element id, which is built dynamically when building a page from the template in the WOD file. Basically, the element id is extended by a number, by components which contains other components (e.g. repetitions and conditionals), so that each component has its own sequence number within the element id for its subcomponents (there are exceptions to this, for some types of components). Since the page can contain different contents depending on what data is available when the page is generated, the element id's can differ each time a page is viewed, which can make it difficult to predict URL's. On the other hand, with the same background data, resulting in identical pages, the URL's should be the same each time (with exception for the session id, of course). With varying data, it would be tricky, but not impossible to predict the correct URL, as long as you now how data has changed. An extra row in a repetition would cause an increase of one of the numbers of the element id. The easiest way to find out which of the numbers it is, is to test by running the application. Johan Carlberg 11 apr 2006 kl. 07.53 skrev Dov Rosenberg: Has anyone decoded the component numbers in the WebObjects URL? |
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [email protected]
