[exprla-devel] Re: [XPL] Re: a domain name for XPL

[reid_spencer <ras...@re...>]

--- In xpl-dev@y..., Lucas Gonze <lucas@g...> wrote:
> >   1. XPL will stream XML data, in an asynchronous and/or
> >      synchronous format, and support multiple streams of
> >      heterogeneous data, including non-XML media types.
...
> From my simple hardware background, "synchronous" means:
> multiple processes are going on;
> their outputs must be combined, and delivered in a correct
> order; to ensure this, processes are
> constrained to open for input or output only on logical
> conditions, which are dependent on a
> global counter or timestamping system.

Async in this context means that messages can arrive at any time
from any party.  This is in contrast to http, where messages come
in request/response pairs and must be initiated by one party (a
browser/client) and never the other (a http daemon).

I would leave streaming to the transport stage - ignore the issue
unless there is a specific reason why you can't.  All it requires
is some type of chunked encoding.

the only language design issue I can think of is that
asynchronous function calls mean function calls that can have 0
or n responses, instead of 1 and always 1 response.  this is a
feature I have never seen in a language.
--- End forwarded message ---