How can I change how single element paths are handled in Seaside? -
seaside default points example.com/myapp
whatever application registered @ myapp
. i'd have core application can handle these links, or other way of handling these links.
so far, have home
application registered default application, http://mydomain.com
resolve it, if generate link, http://mydomain.com/more-info
, seaside tries resolve application registered @ more-info
. if want home
application handle link? or handle in other way?
i'm hosting seaside apache, use apache's url rewriting engine rewrite http://mydomain.com/more-info
http://mydomain.com/home/more-info
, handled home
app.
is there better way this? also, if link exists explanation of seaside request/response lifecycle, that'd sweet.
what trying not common practice in seaside applications. if want generate link 1 page page in application, use callback attached anchor:
html anchor callback: [ self call: moreinfocomponent]
in such cases, not care how url looks , seaside generates url you. such generated urls never have nested structure use parameters.
more information on seaside request/response cycle can found in online book (chapters "fundamentals" , "sequencing components").
however, if indeed want have such nested url (to make urls bookmarkable), there different approaches, depending on want achieve. can either take @ approach handling expired sessions (in book) or @ seaside-rest package.
btw, mapping of urls applications happens through (instances of) wadispatcher. if inspect result of following expression, can see dispatcher tree of seaside. it's entirely customizable adding new applications, dispatchers, etc...
waadmin defaultservermanager adaptors first requesthandler
hope helps on way...
Comments
Post a Comment