Development

Posted by Chris Johnston 12 Jan 2004 23:10 GMT-0000 posts: 4 ☆

Here is how I think implementing the correct MIME type for browsers that can handle it. The reference is at
A link to XML.com that descripted the rewrite rule that could be used for different programs

I am not a rewirte expert but a comment in the referenced document stated to hammer this in somewhere.... I should know where to put it but I'm not there yet.

😀
Also php could be the rewriter although I wonder if the overhead of apache server for a rewrite directive is less than that of global PHP include.
Probably so if it's limited to just the dirctory/virtualomain that holds tiki, BUT can that information be stored with a session cookie.

➡️
I haven't gottin this far into tiki but if the databse is to store information on a user as they vist it could also store the MIME type of the current session.
Can it work this way???

Page request>What type of MIMIE can you take?>Drop session cookie -->display page in acceptable MIME type

Susequent requests->Request session cookie->>Diplay page page using MIME type acceptable for browser

further interaction of MIME type then known via cookie database refernece . Could also state this "MIME sniffing funciton" to be run once at the top of the process tree, a part of getting intial information on clients program abilities and cooking dropping. I think the tiki session cookie comes before the page display. Why not put some login in before dropping a cookie?

Again I have not picked a part tiki yet nor have the expertise in php programming... yet. I dropped this thought for I know asking a user to add stuff to apache is more than what might be expected (permissions?) for a great product that is so flexible.

Chris