Thread: [Rainbowportal-devel] UrlBuilder, Rewrite.Net and Rainbow.Config
Brought to you by:
danijel_kecman,
manudea
From: John M. <joh...@gm...> - 2004-12-31 15:53:58
|
Hi Guys, Been away for a bit due to other commitments and I see a lot has happened while I've been away. I hope the level of activity continues to increase and I hope those of you who have expressed an interest in helping out enjoy working on rainbow. For those of you who would like to contribute and would like to chat via messenger my msnid is howdymatey AT hotmail.com please mention rainbow in the message so I know who you are. As Charles and others mentioned rainbow still has things that need fixing (bugs need fixing, documentation needs updating/to be added and usability issues need to be fixed) and I hope people will continue to submit bugs either via the list or directly to JIRA. I can't guarantee that they'll all be fixed in a timeframe that you guys need (especially those of you who have commercial sites with rainbow) but I think everyone is in agreement that we are better off knowing about the issues than having our heads in the sand. I hope 2005 brings a fresh start with a focus on fixing what needs to be fixed so that people can have a release of rainbow they can build modules, themes, layouts, extensions for and write documentation about. Anyway back to the purpose of my mail. At the moment Urlbuilder and Rewrite.Net settings are spread across web.config and rainbow.config which can lead to confusion when people are trying to figure out what they are doing wrong or how to get rid of the langid and alias from the url. I am thinking of moving these settings into the definition of the provider and the rewrite rule (So that these settings are specific to the way url building/parsing is being done e.g. other providers may not use langinurl as they append all querystring values to the end of the url). e.g: <add name="SqlUrlBuilder" type="Rainbow.Web.SqlUrlBuilderProvider, Rainbow.Provider.Implementation" /> Would become something similar to: <add name="SqlUrlBuilder" type="Rainbow.Web.SqlUrlBuilderProvider, Rainbow.Provider.Implementation" handlerflag="portal" defaultsplitter="-" aliasinurl="false" langinurl="true" /> and the rewrite rule definition settings would become: <RainbowDefaultRule handlerflag="portal" defaultsplitter="-" /> Instead of simply: <RainbowDefaultRule HandlerFlag="portal" /> I would also like to move the rewrite rules so they are closer to the urlbuilder provider definition. I can then add some comments explaining that the settings for your rewriter rule should match the settings for urlbuilder provider implementation (e.g. handlerflag and defaultsplitter should match). This should tidy up the settings a bit and make it easier to understand. One of my new years resolutions is to also write up a doc that explains the settings a bit better and perhaps how to build a rewrite rule and urlbuilder provider if there is interest. Just wanted to run this by you all before applying these changes (I'll add some code that will use the old settings if the new ones are not found for those adding the new dlls to old sites). For those of you that have stress testing/performance tools could you please contact me as I would like to see if a change to the way url builder settings such as keywords, page name, isplaceholder and external link are retrieved improves performance at all). Thanks, John |