Preloading audio - possible in HTML 4 Strict

[Andrew Poulos]

Is there a standards compliant way to preload non-streaming audio (in
HTML 4 Strict)? I did a search and all that I could find was to use the
EMBED tag which is inappropriate.

Andrew Poulos

[Spartanicus]

Andrew Poulos <ap*****@hotmail.com> wrote:

Is there a standards compliant way to preload non-streaming audio (in
HTML 4 Strict)?

Why?

--
Spartanicus

[Andrew Poulos]

Spartanicus wrote:

Andrew Poulos <ap*****@hotmail.com> wrote:

Is there a standards compliant way to preload non-streaming audio (in
HTML 4 Strict)?

Why?

It's needed.

[Michael Fesser]

.oO(Andrew Poulos)

Spartanicus wrote:

Andrew Poulos <ap*****@hotmail.com> wrote:

Is there a standards compliant way to preload non-streaming audio (in
HTML 4 Strict)?

Why?

It's needed.

That doesn't answer the question. Why is it needed? I can't think of a
reason at the moment (except maybe for annoying rollover sound on some
buttons ...) In most cases preloading simply makes no sense.

Micha

[Andrew Poulos]

Michael Fesser wrote:

.oO(Andrew Poulos)

Spartanicus wrote:

Andrew Poulos <ap*****@hotmail.com> wrote:

Is there a standards compliant way to preload non-streaming audio (in
HTML 4 Strict)?

Why?

It's needed.

That doesn't answer the question. Why is it needed? I can't think of a
reason at the moment (except maybe for annoying rollover sound on some
buttons ...) In most cases preloading simply makes no sense.

Nor was my original question answered.

Andrew Poulos

[Alan J. Flavell]

On Wed, 12 Jan 2005, Andrew Poulos wrote:

Nor was my original question answered.

HTML is a markup language for declaring the structure and
characteristics of content. Pre-loading is a client action.
One's adjectival - the other is an imperative verb. If you
don't see the difference, then I'm sorry.

HTML can act as a syntactic *container* for all kinds of things,
including meta http-equiv, javascript, stylesheets, URI references and
so on and so on. Many of those have their own usenet groups where
you'd find answers to questions which address those technologies.

Hence or otherwise deduce that you've already got the best answer that
an HTML authoring group should give you: understand your technologies,
partition your problem, and beware of off-topic answers.

Btw, If I'm forced to wait for your audio to load before I'm allowed
to see your web page, I'll probably have left before I've seen
anything (and of course the audio is muted, because the audio is
dedicated to the videoconferencing application that's running at the
same time). And I'm unlikely to come back. Maybe that's what you
want?

good luck