<div dir="ltr">On Tue, Jul 29, 2008 at 2:52 AM, Kristof Zelechovski <span dir="ltr"><<a href="mailto:giecrilj@stegny.2a.pl">giecrilj@stegny.2a.pl</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div link="blue" vlink="blue" lang="PL">
<div>
<p><font color="navy" face="Arial" size="2"><span style="font-size: 10pt; font-family: Arial; color: navy;" lang="EN-US">Archive: is not generic
enough but perhaps you could bend the URL notation to embrace something like inside:.
I still would not recommend it but it would not make me that sore.</span></font></p>
<p><font color="navy" face="Arial" size="2"><span style="font-size: 10pt; font-family: Arial; color: navy;" lang="EN-US">How about <inside:local/path.html?container=<a href="http://www.site.com/app.jar" target="_blank">http://www.site.com/app.jar</a>>?</span></font></p>
<p><font color="navy" face="Arial" size="2"><span style="font-size: 10pt; font-family: Arial; color: navy;" lang="EN-US">The user agent would be
required to append a query string to local hyperlinks and that parameter would
be reserved (or rename it to h809370dfwhbwa0r92347090).</span></font></p>
<p><font color="navy" face="Arial" size="2"><span style="font-size: 10pt; font-family: Arial; color: navy;" lang="EN-US"></span></font></p></div></div></blockquote><div><br>That query string would have to be appended everywhere you do baseURI + relativeURI -> absoluteURI conversion. So you're really just messing with relative URI syntax for this particular scheme. That's not cleaner than the URI extension for jar:/archive: (or whatever you want to call it), IMHO.<br>
<br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div link="blue" vlink="blue" lang="PL"><div><p><font color="navy" face="Arial" size="2"><span style="font-size: 10pt; font-family: Arial; color: navy;" lang="EN-US">OTOH, you can simulate
several entry points by having all supported entry points on the start page (à
la Microsoft Access) and have the user navigate to what she needs. I do
not think this would be prohibitive from the customer's point of view.
And I am sure there is no need to publish each local address.</span></font></p></div></div></blockquote><div>That breaks bookmarks and similar navigation mechanisms such as intelligent URLbar autocompletion. Also note that an entry point can be a particular document hosted in a Web application, or even a particular email message, so you can't always offer one-click navigation.<br>
</div></div><br>Rob<br>-- <br>"He was pierced for our transgressions, he was crushed for our iniquities; the punishment that brought us peace was upon him, and by his wounds we are healed. We all, like sheep, have gone astray, each of us has turned to his own way; and the LORD has laid on him the iniquity of us all." [Isaiah 53:5-6]<br>
</div>