here is my take on the exact use case that we have with the runmode aware /etc/map it is probably seldomly the case that we actually have different mappings it is just that hostname get into our way.
in the classic wcm authoring or development environment one would still like to see urls that are as close as the ones that we have in production but of course we would not like the links to be rewritten to go fully qualified urls with a domain name... so generally i think the /etc/map tree will look very similar from runmode to runmode but in one every other runmode other than production i would probably either want to put the domain name somewhere in to the url that indicates to the user that this would be a link that would go to http://www.example.org/test in production. so probably could be resolved to something like http://mydev/www.example.org/test . keep in mind though that usually there are only going to be very few link where that would actually make a difference since this assumes that an application has cross domain links under management within one sling instance. to be perfectly honest, for our commercial solution, i think we can do perfectly without the runmode aware /etc/map regards, david On Thu, Dec 10, 2009 at 9:05 PM, Felix Meschberger <fmesc...@gmail.com> wrote: > Hi, > > Bertrand Delacretaz schrieb: >> On Thu, Dec 10, 2009 at 4:53 PM, Felix Meschberger <fmesc...@gmail.com> >> wrote: >>> ...So, I will go for option (1): make the /etc/map location configurable.... >> >> Note that it would be good to be able to find the actual value used >> easily, for example via a console plugin and/or INFO log messages. > > Yes, makes sense. > > Regards > Felix > >> >> -Bertrand >> > -- David Nuescheler Chief Technology Officer mailto: david.nuesche...@day.com web: http://www.day.com/ http://dev.day.com twitter: @daysoftware
