My suggestion then is: 1) Check out the Firefox source code 2) Rewrite the cookie handling code 3) Compile the code 4) ... 5) Profit
On Jan 30, 2008 11:28 AM, Don L <[EMAIL PROTECTED]> wrote: > Extra work, which can easily be saved. > > The logic goes like this: > The use of browser in such case is already determined, that is, for the > general public or the like, hence, it's inappropriate to store cookie etc. > mechanism in such environment. > > >Why can't the institution in question just disable cookies on the > >workstations that they provide? Why should there be a whole new > >version of a given browser (or browsers) when every browser that I'm > >aware of currently allows the people deploying them to configure them > >in the manner that you're describing (e.g. to disable cookies)? -- mxAjax / CFAjax docs and other useful articles: http://www.bifrost.com.au/blog/ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Adobe® ColdFusion® 8 software 8 is the most important and dramatic release to date Get the Free Trial http://ad.doubleclick.net/clk;160198600;22374440;w Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:297700 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4
