[albatross-users] Levelling the "random vs non-random" field

[Matt Goodall]

The other day I was thinking about what _I_ think could make Albatross 
better still. At some point (i.e. if I ever have the time) there are a 
few things I might experiment with in Albatross:

    * Provide random apps with the page lifecycle (specifically
      page_enter and page_leave) that non-random apps benefit from -
      it's a wonderful way to manage session data. This is probably more
      difficult but I suspect it's not impossible. The session already
      has __page__ so I think Albatross has enough to work out what's
      going on, it's just putting the hooks in the right place?
    * Make ctx.set_page() and ctx.redirect() work for both types of
      apps. I think this is one of the few cases where Albatross forces
      you to decide on an application type right at the start and I
      think that's a shame. Perhaps it's even unnecessary? I don't know yet.
    * Make a RandomPageObject mixin. Or better still, separate the
      random vs non-random and page object vs page module behaviours to
      allow whatever combination makes sense. I don't think this would
      be too difficult and it may be quite useful.
    * More request adapters. The one I'm probably most interested in is
      Twisted. Twisted is a lot of fun and has some some really nice
      features but woven (the web part of the framework) is more complex
      than something like Albatross.

What are your thoughts on the above? Have you explored any of these 
already and decided its too difficult? Dave/Andrew, is there anything 
that you simply don't want to see happening in Albatross?

Of course, I may never actually find any time to look into any of these ;-)

Cheers, Matt

-- 
Matt Goodall, Pollenation Internet Ltd
w: http://www.pollenationinternet.com
e: matt at pollenation.net