Ok, thanks.
On Wed, Oct 2, 2019, 4:16 PM Matthew Flatt wrote:
> At Wed, 2 Oct 2019 11:06:14 -0400, David Storrs wrote:
> > On Wed, Oct 2, 2019 at 8:42 AM Matthew Flatt wrote:
> > > It depends on `process-file`. If `process-file` retains `msg` until it
> > > is otherwise done, then yes. But if
At Wed, 2 Oct 2019 11:06:14 -0400, David Storrs wrote:
> On Wed, Oct 2, 2019 at 8:42 AM Matthew Flatt wrote:
> > It depends on `process-file`. If `process-file` retains `msg` until it
> > is otherwise done, then yes. But if `process-file` ignores the argument
> > for `msg` or only uses it for the
On Wed, Oct 2, 2019 at 8:42 AM Matthew Flatt wrote:
>
> At Tue, 1 Oct 2019 23:52:05 -0400, David Storrs wrote:
> > ; main dispatcher loop in the server. Receives messages, dispatches
> > to child thread for processing
>
> > 2) This WOULD work:
> > (let loop ()
> > (define msg
At Tue, 1 Oct 2019 23:52:05 -0400, David Storrs wrote:
> ; main dispatcher loop in the server. Receives messages, dispatches
> to child thread for processing
> (struct file-info (hash) #:transparent)
> (define channels (make-weak-hash))
> (let loop ()
> (define msg (get-next-message)) ;
I have a server with a main dispatcher loop that receives messages and
farms them out to processing threads. I'd like to have able to have
later messages inform the behavior of earlier message processing -- an
example would be "message 1: here is a file to download" followed by
"stop downloading
5 matches
Mail list logo
