Re: Any advice on URL to component mapping before I dive in?
Karsten Kusche <[email protected]>
| Newsgroups | gmane.comp.lang.smalltalk.squeak.seaside |
|---|---|
| Message-ID | <[email protected]> |
The URLs are resolved via Resolver objects, i.e WADispatcher/WAApplication objects. Once your application is asked to handle a URL, it’ll instantiate its root component and render it. Your root component instance will once receive an #initialRequest: call. There you can handle the rest of the URL and take appropriate actions. The parameter is a WARequest with a URL but you should ask the current RequestContext for its #consumer instead. That way you can proceed analysing the path independent of the path of your application (that’s especially important once you’ve running behind a reverse proxy). Karsten Am 10. November 2018 um 08:30:14, gettimothy ([email protected]<mailto:[email protected]>) schrieb: Good morning. Thanks to the folks who wrote the Twitter Bootstrap, I figured out how to change the URL so that the URL reflects the current path in the application. For example, like this: http://menmachinesmaterials.com/zurb/BuildingBlocks/Containers/CSSMasonryGrid However, that URL WILL NOT take you directly to the component. That is what I would like to implement. The Seaside Book appears to touch on this with their REST Services section, so I have that to go on. I figured I would ask the board before I tackled this task. Thank you in advance. tty _______________________________________________ seaside mailing list [email protected] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside _______________________________________________ seaside mailing list [email protected] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside