Hello,
I've been doing a little experiment with Polycephaly & Seaside recently.
The basic idea was to launch & control multiple Seaside instances.
One problem I encountered was that Polycephaly communicates via standard
pipes (stdout/in/err). As soon as the drone image writes some text to
stdout, the master listener receives this text and tries to unmarshal it
with BOSS, which raises an error.
Drone>>initializeTranscript tweaks the Transcript to write to stderr.
But stdout is a rather popular output for console applications, e.g.
when a command line tool is forked, it will write to stdout by default,
and thus break the communication.
I would prefer a dedicated communication pipe to avoid this problem.
_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc
Locked
