Hi All, I'm just throwing together a virtual domain behaviour, eg map dir.example.com internally to example.com/dir/. I got a prototype working, but when adding the code to select a child page based on the host name I ran into a problem: I can't see an easy way to get at the request object.
I thought about making Behavior::Base#process to check for parent behaviour, like in Behavior::Base#page_url, but that doesn't work as then the parent behaviour's page would be rendered, not the correct child (unless i followed the code incorrectly). My next thought is to pass the request/response through when asking for the parent's behaviour, but this does couple everything together a bit much. Another approach would be to make attr_accessor()s on behaviours and fill them in after we get the parent page's behaviour. I'm going to try the attr_accessor method, and see how far i get, but i was wondering to see what John and other people thought... Any comments? Bodhi _______________________________________________ Radiant mailing list Radiant@lists.radiantcms.org http://lists.radiantcms.org/mailman/listinfo/radiant
