Rick Potts wrote:
> Below is a list of the flags that I think should be specified... The
> flags are broken into funtional catagories (general, cache, session
> history)....
>
> general flags:
> -------------
> + bypass URI fixup on string (assume string is already a wellformed URI)
there are at least two stages of URI fix-up: pre-loading (i.e.
prepending "http://"; to the string), and post-loading (i.e. munging a
URI into something else, a keyword: URI for example, if the load failed
(perhaps a DNS failure for example)). would/should this flag bypass
*all* fixup stages?
> One issue that i have is whether there should be flags to control
> "global history" as well as "session history". Currently, there is no
> way to prevent URIs from being added to "global history" via these
> flags...
you can snuff out a global history addition in a round-about manner by
providing your own nsIGlobalHistory implementation and doing some ugly
trickery to ensure that specific URI's aren't added, but, that falls
well outside the context of "load flags." I can't think of a case where
you'd want to bypass global history, but, for parity's sake, it probably
makes sense to add the flag. I guess I can see someone wanting to
implement an "privacy" feature where-in no URI strings are cached.
Jud
