About MIDI: you can play MIDI files, you just have to manualy add
your player to MIME.CFG. About background MIDI... well, in fact, EMBED
tag issue was postponed for reasons like ... see below.
About Shockwave: yes, it is nastym, and it is cookie related, I think.
Sometimes, mixing cookies and redirection makes problems, I did my
best to understand what browser are expected to send - if someone knows
*exactly*, or know RFC document which specifies it, please let me know.
I am talking about correct combination of which HTTP-referer and which
Cookie HTTP header lines are expected by server, when browsers gets
both Set-Cookie: and Location: response from the server at the same
time. I mean: is HTTP referer the original page, from which entire
handshake started, or is it always the previous URL, which returned
Location: ? Shoul Cookies for same domain/path accumulated or
overwritten ? etc., etc. Please help, please point me to some docs...
I believe, that as soon as we can demontrate, that Arachne can view
the pages without problems, it won't be such a big problems to become
listed in databases of browsers supported by major servers like
Shockwave...BTW there may be (it is not sure, but there is some
technical chance) Flash plugin available for Linux builds of
Arachne, if I succesfuly negotiate with certain busines partners... so
we would have both MP3 streams and Flash in Arachne - Flash is IMHO much
better than original Shockwave, BTW.. .it is done by the same company...
--
Michael Polak: [EMAIL PROTECTED]
Arachne Labs: http://arachne.cz/
My mobile phone - up to 160 characters: [EMAIL PROTECTED]
