In this case, it is worth noting that browsers would want to have
message caching so that the incoming response doesn't destroy the
document you are currently viewing. In other words, there would
have to be a cache mechanism on the client side for responses based
on MOLTIP UID's or something so that you could tell multiple messages
from different servers apart in the queue.
Maybe a window with a Netscape-hotlist style interface would work, but
it would be separate from the hotlist in implementation unless a link
to your list was specifically requested.
Anyway, something to consider.
> [*] I didn't include the details on "R-HTTP" here to avoid
> making this an excessively long mail.
>
Actually, it would help your argument quite a bit to give more details.
-- _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ Adam T. McClure Integrated Teaching & Learning project mcclurea@colorado.edu University of Colorado-Boulder"When philosophy has grown beyond science, it is time to create a new science." --
"Any sufficiently advanced technology is indistinguishable from magic." -- Arthur C. Clarke _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ "