> > why isn't it designed to work this way? That's the very same way
>HTML works.
>
>HTML goes from beginning to end.
Anthony,
I beg to differ: an HTML page contains the HTML code, and the names
of additional files (IMG SRC tags, EMBED tags etc.) which are also
downloaded. Each page of a web site is a separate file. Thus, if
you're approximating an HC stack with an HTML page, the stack would
be the index page, and each card would be an HTML page, and each
button might be an embedded custom content type or whatever. I don't
want to do this!
Instead, I want to go by the same principle: There is one file that
is the stack, containing the stack script, and a list of the card
filenames. Then there's one file for each card, which in turn
contains a list of file names for the buttons on that card (hidden
buttons don't need to be downloaded right away). I guess this would
work effective enough but wouldn't require us to invent our own
streaming protocol for web-deployment of stacks.
But I don't know the insides of FTP, HTTP etc. that well, so I'm
ready to stand corrected.
Cheers,
-- M. Uli Kusterer
------------------------------------------------------------
http://www.weblayout.com/witness
'The Witnesses of TeachText are everywhere...'
