From: Nicholas Paul Johnson <nickjohnson@virginia.edu>
Cc: nickjohnson@virginia.edu,
Faraz Shahbazker <faraz_ms@rediffmail.com>,
guile-user@gnu.org
Subject: Re: to serialize/deserialize closures; and multithreading
Date: Fri, 26 Mar 2004 10:22:03 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.4.44.0403261021360.17741-100000@localhost.localdomain> (raw)
In-Reply-To: <20040326130518.GA5385@www>
Wow,
This is almost exactly what I was looking for... thanks.
--
Nicholas Paul Johnson
nickjohnsonSPAM^H^H^H^H@virginia.edu
http://manjac.ath.cx/nick
_
( ) ascii ribbon campaign - against html mail
X - against microsoft attachments
/ \ http://www.google.com/search?q=ascii+ribbon
--
On Fri, 26 Mar 2004 rm@fabula.de wrote:
> On Thu, Mar 25, 2004 at 10:38:00PM -0000, Faraz Shahbazker wrote:
> > nick,
> >
> > I am curious too : what is your purpose of migration?
> >
> > I am working on something similar, for using scheme on
> > Beowulf-clusters with PVM. Here the purpose of migration is to
> > remotely-evaluate a sexp. But possible uses of this technology
> > could be to simply suspend/restart programs(see chpox), or for
>
> Just out of _my_ curiosity: are you aware of 'kali' -- a reborn
> MIT scheme that supports distributed computing?
> For yet another 'transport' layer for S-Expresive Data have
> a look at FramerD (former MIT project, now at sourceforge,
> <http://www.framerd.org> -- erm, some basic Guile bindings for
> that can be found at http://cvs.zeit.de (beware: highly experimental
> code with bitrot!).
> >
> > > Should a mutation on the new computer of a captured variable
> > > affect the old computer? - greg
> >
> > Basically, if your program is purely/mostly functional,
> > it might be easy to migrate, while maintaining referential
> > transparency - just byte-copy(with tags) all data-types.
> > The semantics of mutable objects (when mutation does occur)
> > is for you to decide. It might make greater sense for example
> > for exceptions to be migrated and handled remotely, than
> > say mutexes or ports.
>
> Autsch, that does get rather expensive when closures/continuation
> are used (something that does happen occasionally in functional
> programming ;-).
>
>
> just my 0.02$,
>
> Ralf Mattes
>
>
_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-user
next prev parent reply other threads:[~2004-03-26 15:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-25 22:38 to serialize/deserialize closures; and multithreading Faraz Shahbazker
2004-03-26 13:05 ` rm
2004-03-26 15:22 ` Nicholas Paul Johnson [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-03-26 20:02 Faraz Shahbazker
2004-03-26 20:35 ` Andreas Rottmann
2004-03-25 6:19 Nicholas Paul Johnson
2004-03-25 6:43 ` Paul Jarc
2004-03-25 12:40 ` Greg Troxel
2004-03-25 17:18 ` Lynn Winebarger
2004-03-25 18:11 ` Lynn Winebarger
2004-03-25 19:55 ` Paul Jarc
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.44.0403261021360.17741-100000@localhost.localdomain \
--to=nickjohnson@virginia.edu \
--cc=faraz_ms@rediffmail.com \
--cc=guile-user@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).