Hello Marcus, >>> If you notice my latest wiki edit (5 minutes ago) I have read the >>> holy >>> standard and come to favour the fragment feature of url for zip- >>> files, >>> i.e. http://server/archive.zip#file.obj). (Several zips/archives >>> would >>> then just be several # in a row.) >> >> That does not work. Consider having a relative URL "images/foo.jpg" >> inside file.obj. This will be transformed to the absolute URL >> "http:// >> server/images/foo.jpg", instead of the correct URL "http://server/ >> archive.zip#images/foo.jpg". There is a reason why Sun developed that >> ugly jar URL scheme ("jar:http://server/archive.jar!foo.class";), >> instead of using fragments... > I don't see why the transformation would have to ignore the # ? .. (It > would remove only file.obj.. not archive.zip#file.obj .. back up > only to > the first / _or_ # .)
Because the rules for transforming relative (http/file/ftp) URLs to absolute URLs say that relative URLs are relative to the "path" part of the HTTP URL and not to the "fragment" part. > As I said, I'm no URL expert. I do not see the difference between > using > # and ! in your example. (Given that I write the transform code > myself. > Or are the standard rules which govern that?) The crucial point here is not using ! instead of #. The crucial point is that Sun introduced a new URL scheme "jar:" where relative URLs are resolved differently (compared to http/file/ftp URLs). Look carefully at my example - the URL starts with "jar:", not with "http:". Bye, Patrick ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Opensg-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/opensg-users
