For the project I am currently working on, I have the following design thought.
I've written a database Provider module that will turn the url http://foo.com/bar/<key>.xml and provide the xml formatted results for the sql query select <fields> from <table> where <keyfield> = <key> where <fields> and <table> and the database connection parameters are taken from a .htaccess file in /bar I would then like to be able to use http://foo.com/bar/<key>.xml/<style> to handle various diffrent views of the record, including such things as edit forms ect, then also be able to apply some conditional stylesheets after the <style> pipeline to account for the method that the user is using to access the system.. aka MSIE, Mozilla, Opera, WAP, ect.. Also.. It would be nice to be able to do http://foo.com/bar/<key>.pdf and get a PDF render of <key>.xml at the same time allowing for the http://foo.com/bar/<key>.xml/edit syntax for editing the edit form for the record. potential problems.. In the case of the edit form(s), using logic sheet(s) infront of the XSP stage will mean that it likely will not be cashable, which I believe means that performance will be closer to running a CGI rather than direct unmodified Apache file access. Also, I am wondering, would the xml record => logic sheet => XSP works well with the PerForm taglib library. and what considerations would need to be made when doing so. Thanks for the help, -Robert Ferney --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
