On Wed, Nov 2, 2011 at 3:12 AM, dokondr <span dir="ltr"><<a href="mailto:dokondr@gmail.com">dokondr@gmail.com</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Thanks everybody for advice!<br>I'll try to clarify what I mean by persistence and concurrent access that preserves "happens-before" relationship.<br>1) Persistence - imagine Haskell run-time executing in infinite physical memory. My idea is to implement really huge, "almost infinite memory" in the cloud of one or another type. Nothing more nothing less, nothing imperative, exactly the same environment that GHC runtime works today, but extended to huge virtual memory in the cloud.<br>
<br></blockquote><div><br>I am afraid I am confused everybody, didn't mean it, sorry. I understand that infinite physical memory is not quite the same that implementing NData.* on top of some cloud framework. Yet NData.* may be the first step in this direction. Infinite memory will require support in Haskell run-time, run-time distributed across many physical instances. Yet, it looks like physical memory will eventually will be very huge virtual memory persistent in the cloud for some period of time. IMHO this will simplify programming model considerably.<br>
<br></div></div>