|
|
Posted by Jonathan N. Little on 11/19/27 11:46
cwdjrxyz wrote:
> frederick wrote:
>> I've just come across a link to this odd-looking URL:
>> http://www.prbm.com/interest/i.htm?manuscripts-d-f.shtml~main
>>
>> Can anyone enlighten me as to use of the "~main" at the end?
>
> It appears that you have received the correct answer. Actually there
> are many odd-looking URLs, and many of these are associated with media.
> If you go to the new Google video service and examine how they link to
> various free video files, their special Google player, etc, you will
> find many unusual URLs used as well as a special extension for the
> Google player. Also there are some very long ones that run over 2 or 3
> lines. Also when you call a streaming media file on a streaming Real or
> Windows Media server you often use a URL structure not used elsewhere.
> As one example, when you are using a recent Real Player to display a
> SMIL page, you code for a progressive download video, image, music, etc
> may start with either the usual http://... or chttp//... . Using the
> "c" at the start of the url tells the Real player to cache what you
> called in a special Real player cache so that it does not have to be
> reloaded at a second pass.
>
Yes, but what you are describing is the protocol part of the url and has
nothing to do with the OP. The OP's situation is pseudo query string
that with JavaScript is used to select a frame to be displayed in a
attempt of overcome the shortcomings of frame whereby only the outermost
containing frame is 'visiable' in the URL. Best solution would be to
abandon the frames or at least employ a real query string and use
server-side scripting to select the internal frame.
--
Take care,
Jonathan
-------------------
LITTLE WORKS STUDIO
http://www.LittleWorksStudio.com
Navigation:
[Reply to this message]
|