<?xml version="1.0" encoding="ISO-8859-1"?>

<!DOCTYPE message PUBLIC
  "-//MLarc//DTD MLarc output files//EN"
  "../../mlarc.dtd"[
  <!ATTLIST message
    listname CDATA #REQUIRED
    title CDATA #REQUIRED
  >
]>

  <?xml-stylesheet href="../../mlarc.xsl" type="text/xsl"?>


<message 
  url="2006/02/e9a18d1cb4053c82e47fc6c85ff98215"
  from="Jonathan Roewen &lt;jonathan.roewen@g...&gt;"
  author="Jonathan Roewen"
  date="2006-02-07T22:03:34"
  subject="Re: [Caml-list] Re: async networking"
  prev="2006/02/e89bba942ce6fd287e9d3d72aaa93335"
  next="2006/02/2858f1e4532daae90d5b0762e3fff3cd"
  prev-in-thread="2006/02/e89bba942ce6fd287e9d3d72aaa93335"
  next-in-thread="2006/02/4c274ae5cdd22d113ed70a1f4b75149e"
  prev-thread="2006/02/b801b6e1958639194014abd51a4747a3"
  next-thread="2006/02/1df604b17c7343a34edde8c4272eced3"
  root="../../"
  period="month"
  listname="caml-list"
  title="Archives of the Caml mailing list">

<thread subject="async networking">
<msg 
  url="2006/02/97ace0c2a51e26bcec579188e650a0e3"
  from="Rick Richardson &lt;rick@e...&gt;"
  author="Rick Richardson"
  date="2006-02-05T08:52:13"
  subject="async networking">
<msg 
  url="2006/02/60ec1632c3246656d7b42c04b18ad63f"
  from="Gerd Stolpmann &lt;info@g...&gt;"
  author="Gerd Stolpmann"
  date="2006-02-05T17:32:21"
  subject="Re: [Caml-list] async networking">
<msg 
  url="2006/02/1b2095ecd7a2ec4b5bd81a466b1767ea"
  from="Bardur Arantsson &lt;spam@s...&gt;"
  author="Bardur Arantsson"
  date="2006-02-06T18:36:02"
  subject="Re: async networking">
<msg 
  url="2006/02/94a4dea725ed48b6b931f9224e2e9dfd"
  from="skaller &lt;skaller@u...&gt;"
  author="skaller"
  date="2006-02-07T04:55:37"
  subject="Re: [Caml-list] Re: async networking">
<msg 
  url="2006/02/ae6f50d034714c0e8551bc0415d4cf42"
  from="Bardur Arantsson &lt;spam@s...&gt;"
  author="Bardur Arantsson"
  date="2006-02-07T17:45:31"
  subject="Re: async networking">
<msg 
  url="2006/02/cb7d30ceda032a7b784aefe7eb3b802a"
  from="Gerd Stolpmann &lt;info@g...&gt;"
  author="Gerd Stolpmann"
  date="2006-02-07T19:01:12"
  subject="Re: [Caml-list] Re: async networking">
<msg 
  url="2006/02/8c0b2f7ae1934f13f6e2fe7f472b292c"
  from="Bardur Arantsson &lt;spam@s...&gt;"
  author="Bardur Arantsson"
  date="2006-02-07T19:44:46"
  subject="Re: async networking">
<msg 
  url="2006/02/9de2330188f2388caa317c2fb0112441"
  from="Gerd Stolpmann &lt;info@g...&gt;"
  author="Gerd Stolpmann"
  date="2006-02-07T20:30:32"
  subject="Re: [Caml-list] Re: async networking">
</msg>
<msg 
  url="2006/02/49f627717d14a6d636ed4b42a4ed94bd"
  from="Remi Vanicat &lt;remi.vanicat@g...&gt;"
  author="Remi Vanicat"
  date="2006-02-07T20:51:17"
  subject="Re: [Caml-list] Re: async networking">
</msg>
</msg>
</msg>
<msg 
  url="2006/02/00d09a52e6daa7b06dc961b0f30d2b4e"
  from="Rick Richardson &lt;rick@e...&gt;"
  author="Rick Richardson"
  date="2006-02-07T19:28:11"
  subject="Re: [Caml-list] Re: async networking">
</msg>
<msg 
  url="2006/02/e89bba942ce6fd287e9d3d72aaa93335"
  from="Rick Richardson &lt;rick@e...&gt;"
  author="Rick Richardson"
  date="2006-02-07T21:31:48"
  subject="Re: [Caml-list] Re: async networking">
<msg 
  url="2006/02/e9a18d1cb4053c82e47fc6c85ff98215"
  from="Jonathan Roewen &lt;jonathan.roewen@g...&gt;"
  author="Jonathan Roewen"
  date="2006-02-07T22:03:34"
  subject="Re: [Caml-list] Re: async networking">
<msg 
  url="2006/02/4c274ae5cdd22d113ed70a1f4b75149e"
  from="Rick Richardson &lt;rick@e...&gt;"
  author="Rick Richardson"
  date="2006-02-08T04:18:07"
  subject="Re: [Caml-list] Re: async networking">
<msg 
  url="2006/02/ffd3c37c09ea8166f8864f74f592246e"
  from="Markus Mottl &lt;markus.mottl@g...&gt;"
  author="Markus Mottl"
  date="2006-02-08T14:43:56"
  subject="Re: [Caml-list] Re: async networking">
</msg>
</msg>
</msg>
<msg 
  url="2006/02/5e5554587406ae917e5112a1f20ca1af"
  from="skaller &lt;skaller@u...&gt;"
  author="skaller"
  date="2006-02-08T04:29:27"
  subject="Re: [Caml-list] Re: async networking">
</msg>
</msg>
</msg>
</msg>
</msg>
</msg>
<msg 
  url="2006/02/1276c935a6702530a86debf1fa1627c5"
  from="Pierre Etchemaïté &lt;petchema@c...&gt;"
  author="Pierre Etchemaïté"
  date="2006-02-05T20:18:08"
  subject="Re: [Caml-list] async networking">
</msg>
</msg>
</thread>

<contents>
&gt; The multiple serving threads could actually make for an simple api,
&gt; actually. A simple function to add a receive callback for a port would
&gt; be all you'd need. You could even pass in a buffer to that callback that
&gt; a person could respond directly to for socket send, since the same
&gt; thread is handling the send requests as well.

I haven't checked the systhreads implementation (as I don't use it),
but if it's anything similar to the vmthreads implementation, it is
not very high performance.

For example: to reschedule a thread, vmthreads a) uses select (not
sure if this is a problem), and b) does a linear search for a runnable
thread (I can't remember if it stops early, I'd have to have another
check).

The point is, in this case, you'd need to rewrite it to use thread
queues for the various states to get something closer to an O(1)
scheduler.

Jonathan

</contents>

</message>

