Hi folks,

This is addressed mainly to Martin Kobetic and Nicholas Cellier,
who've done the Squeak port of Xtreams from VisualWorks, but I thought
I'd post here in case anybody else has an opinion to share.

I've been working on integrating Filesystem and Xtreams, and I'm a bit
puzzled by the XTExternalResourceHandle hierarchy. In particular, I
can't figure out why XTIOHandle exists. It seems to have functionality
needed by XTIOSocketHandle, plus some indirection for hiding which
classes are used for file or socket handles, even though there's only
one choice for either of those. I'm guessing this has to do with the
need for Xtreams-Terminals to be VW-compatible, and that this
hierarchy is needed on VW.

What I need to do is create different versions of XTIOFileHandle that
can provide access to data in alternate filesystems - in-image, inside
a zip file, on a remote host etc. Ideally, I'd extract the primitives
into a separate object, and provide alternate sets of "primitives" for
non-native filesystems. I don't want to get into changing things
without understanding the status quo, though.

Thoughts?

Colin