No subject

part from the async behavior of threads).<br><div class=3D"gmail_extra"><br=
><br><div class=3D"gmail_quote">On Sat, Nov 10, 2012 at 8:55 PM, Kevin Tew =
<span dir=3D"ltr">&lt;<a href=3D"mailto:tewk at cs.utah.edu" target=3D"_blank"=
>tewk at cs.utah.edu</a>&gt;</span> wrote:<br>

<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
 =20
   =20
 =20
  <div text=3D"#000000" bgcolor=3D"#FFFFFF">
    <div>I&#39;m not sure I understand your
      question.<br>
      But you need to wrap your input events with handle-evt or wrap-evt
      so you can close over state that helps you distinguish the events
      when sync returns.<br>
      <br>
      Kevin<div><div class=3D"h5"><br>
      On 11/10/2012 10:55 AM, Laurent wrote:<br>
    </div></div></div>
    <blockquote type=3D"cite"><div><div class=3D"h5">Hi,<br>
      <br>
      Can a single &#39;sync&#39; accept several input-port events?<br>
      From my little tests, it seems not, but this does not seem to
      match what the docs say.<br>
      To make it work and avoid one of the clients to be blocked half of
      the time, I needed to run several sync&#39;s in different thread. But
      then I don&#39;t see the interest of using &#39;sync&#39; over a norm=
al
      &#39;read&#39;.<br>
      <br>
      Thanks,<br>
      Laurent<br>
      <br>
      <fieldset></fieldset>
      <br>
      </div></div><pre>____________________
  Racket Users list:
  <a href=3D"http://lists.racket-lang.org/users" target=3D"_blank">http://l=
ists.racket-lang.org/users</a>
</pre>
    </blockquote>
    <br>
  </div>

</blockquote></div><br></div>

--047d7b3398596012ec04ce29d4ed--