[14:02]<mib_wp5i98> hi [14:02]<zumbrunn> hi mib_wp5i98 [14:03]<mib_wp5i98> how can i make the root object act like another hopobject [14:03]<zumbrunn> actually, that is what it does by default [14:04]<zumbrunn> root is an instance of the Root prototype, which by default inherits from the HopObject prototype [14:05]<mib_wp5i98> i want do use another node in dependency of the requsts subdomain as root [14:06]<zumbrunn> ok [14:07]<zumbrunn> if I would know an easy way to do that, I would do it myself [14:07]<zumbrunn> currently I just redirect to other objects in those kinds of situations [14:08]<zumbrunn> and others usually use apache and mod_proxy or similar to mapp incoming domains to different helma apps [14:08]<zumbrunn> generally, the idea is that an app only has one root object [14:08]<mib_wp5i98> antville is acting in that way, but i dont know enough about is. i will study it an maybe come back later [14:08]<simono> antville is switching root? [14:10]<mib_wp5i98> i dont know, but its behavior is like that. [14:11]<zumbrunn> I guess one could code the behavior of root in a way that the actual lookup of properties and child collections happens on other objects [14:11]* zumbrunn is trying to remember how antville behaves