-
Notifications
You must be signed in to change notification settings - Fork 71
Naming URLs
Philippe Marschall edited this page Sep 13, 2018
·
1 revision
To set the path, implement #updateUrl:
in your components. This will get passed a WAUrl
instance, which responds to #addToPath:
and #addParameter:value:
. Each active component gets a chance to modify it before every redirect and response.
To initialize your app, implement initialRequest:
. This will be sent at the beginning of the session, and gets passed a WARequest
instance. Typically you will want to use the information in the request to construct the root component.
See WABrowser
for an example.
An other approach is to use WARestfulComponentFilter
.
Changelogs
- (newer changelogs, see https://github.com/SeasideSt/Seaside/releases)
- 3.4.0
- 3.3.0
- 3.2.4
- 3.2.2
- 3.2.1
- 3.2.0
- 3.1.3
- 3.1.2
- 3.1.1
- 3.1.0
- 3.0.11
- 3.0.9
- 3.0.8
- 3.0.7
- 3.0.6
- 3.0.5
- 3.0.4
- 3.0.3
- 3.0.2
- 2.8
- 2.7
- Past Releases
Development
Documentation
- Configuration and Preferences
- Embedding Subcomponents
- Maintaining State
- Generating HTML
- CSS and Javascript
- Debugging Seaside Applications
- Links, Forms and Callbacks
- Development Tools
- Call and Answer
- Naming URLs
- Security Features
- Securing Seaside Applications
- Seaside-REST
- Add-On Libraries
- Persistence
- Gettext
- FileLibrary
- The Render Tree
- PDF Generation
- Long-Term Issues
- Ajaxification
- Web Components
- Big Issues
Sprints