[albatross-users] Random pages and application model

[Matt Goodall]

Oops, my post was supposed to go to the list. Hope you don't mind me
forwarding your reply Mike.

Cheers, Matt

On Fri, 2003-02-21 at 22:39, Michael C. Neel wrote:
> Hmmm... I guess I misuse the non-random module then ;)  I usally set a
> page member variable on the page object, and set that from the request,
> so that pages are able to be bookmarked, unless I do an interal switch,
> for a thank-you page or something that I don't want to be bookmarked.  I
> then "switch" off of this variable in process().
> 
> One of my hobby sites, www.fistsofniall.com is this way.  In fact, you
> can't even tell that it's using *any* form of server side application
> from the urls (all though that site doesn't have much in the way of
> form, just a lot of dynamic content from a database).
> 
> Mike
> 
> -----Original Message-----
> From: Matt Goodall [mailto:matt at pollenation.net] 
> Sent: Friday, February 21, 2003 5:19 PM
> To: Michael C. Neel
> Subject: RE: [albatross-users] Random pages and application model
> 
> 
> On Fri, 2003-02-21 at 14:56, Michael C. Neel wrote:
> > >Page_display() is called to display a page (der!) and may not
> > necessarily be
> > >called in conjunction with anything else (e.g. if the user hits
> > "refresh").
> > 
> > >When the user submits a form, then page_proces() is called.  If
> > page_process()
> > >calls set_page(), then page_leave() and page_enter() will be called.
> > But it
> > >is perfectly valid for page_process() not to change the current page,
> > in which
> > >case page_leave() and page_enter() will not be called.   
> > 
> > Is this correct?  In my time with Albatross, it seemed that 
> > page_process and page_display were called for every request,
> submission or no.
> 
> The description above seems correct from what I've seen. For non-random
> pages, page_process() is only called to process an action (form
> submission, link click etc) for the page.
> 
> > I've
> > never needed beyond the SimpleApp, so that might have something to do 
> > with it.  I haven't yet figured out what the other page methods offer 
> > that is not doable in SimpleApp (not the session mixins, just the page
> 
> > mixins).
> 
> They all let you do the same thing but in a different way.
> 
> The only real difference I've seen between the PageObjectMixin and the
> PageModuleMixin is how your application is structured. You're probably
> best reading section 4.6 of the manual for more.
> 
> The difference between random and non-random mixins is a bit more
> interesting ...
> 
> The non-random page mixins are great for truly stateful applications,
> i.e. something like an administration system or a webmail application. I
> think "application" is probably the key word here. The request URL for
> these apps always stays the same no matter which page is displayed.
> 
> The random page mixin is useful for your more traditional,
> content-oriented website. The key difference is that the random mixin
> uses the request URL to determine the page to display and, more
> importantly, changes the request URL to move to a different page. That
> gives the user something useful to bookmark which is pretty important in
> many situations.
> 
> Hope that helps.
> 
> Cheers, Matt
> 
> > Mike
> > _______________________________________________
> > Albatross-users mailing list Albatross-users at object-craft.com.au
> >
> https://www.object-craft.com.au/cgi-bin/mailman/listinfo/albatross-users
-- 
Matt Goodall, Technical Director
Pollenation Internet Ltd, http://www.pollenation.net
e: matt at pollenation.net
t: 0113 2252500