On Saturday 28 September 2002 06:05, Robert Barta wrote: > This is interpreted by the above AxKit::XSP::Blogs package which fetches > the data and passes on the blog in some XML format (BTW: is there a > 'standard' already for this?). The rest is up to usual AxKit rendering. > > I wonder whether this is the 'AxKit' way of doing this? When exactly > should you write a 'provider'?
You would use XSP if the act of calling the page may have side-effects. One example is a form mailer, another one would be the entry form of your blog. For "constant" access to some data, a provider is much more useful, as you only need to provide a last-modified timestamp and get automatic caching for all pages based on your provider. For example, I use a mysql TIMESTAMP field on all SQL tables I intend to serve through a provider, getting the required last-modified timestamp for 'free'. I also have a generic SQL provider configured via .htaccess which I may make available if you are interested. One notable thing about providers is that you are not required to keep your configuration info in XML files. SO instead of creating a phony XML file with your <blog .../> tag you can choose a different way to specify data source and access information. CU J�rg --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
