Hello Meikel, ah, interesting. I didnt know about seque. That sound fit. Cool!
The answers may return in different order for different reasons. A: Q1 -some question A: Q2 - "Are you still alive." B: A2 - "Alive an kicking." B: A1 - some answer. A: A3 - other question B: Info: Service paused. ... So, seque sounds right at the first stage - the sequence of lines. The second stage - sequence of messages might need some reordering or different approach. Thanks a lot, alux On 15 Apr., 14:32, Meikel Brandmeyer <[email protected]> wrote: > Hi, > > On Apr 15, 2:10 pm, alux <[email protected]> wrote: > > > Its streams, I completely agree. > > Might answers return in different orders? > > Fred: What do you think about the Smith contract? > Fred: Left at the lights, right? > Bob: yes, left > Bob: uncomfortable > > > And now I'm not sure whether the blocking permits to be a sequence. As > > far as I understand, blocking (in the Clojure world) should be > > restricted to references. And if head and tail of a "seq" are > > references, they dont fit the interface anymore, or do they. > > Maybe seque? You can feed it with answers on one end. When the client > (pulling of at the other) gets ahead, he blocks. > > Sincerely > Meikel -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to [email protected] Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/clojure?hl=en To unsubscribe, reply using "remove me" as the subject.
