Hello,

it depends on what you mean by common internet file system...

Common communication standards are always a good thing and depending on what
you inten to communicate, you might look at using/adapting/ripping-off :-) XML
but there are others working on this. Look for XML work and align yourself
accordingly. XML has many advantages.

Sharing code between machines without filing-out and in requires a shared
common code base, an object repository, like CSV for Unix/Linux or PVCS for
Windows & OS2, to check-out code, (class and method definitions) so that
collaborators won't clobber changes you might be making and to check-in the
code when you're done unit testing.

That how Visual Smalltalk Enterprise and ENVY/Developper do it and that how its
done for every other document type in addition to code. Don't even think it can
be done any other way. They have all been tried over the past three decades and
this is the _one_ way that has survived...)

If you meant something else by "Common Internet File System" then I may have
been off-base and pointing you to the wrong things. (Since the file system is
an OS function, we're pretty much stuck with the ones installed on the
underlying platforms.)

-Charles-A.

Mayuresh A Kathe wrote:

> Hi,
>
> I had posted this earlier but got no response.
>
> So I assume that I'll have to work on this alone, I wouldn't mind that but
> would like to know whether it would really be usefull to have an
> implementation of the CIFS for Squeak, whether sharing files across
> computers via squeak would really help us in collaboration.
> Else I'll drop the idea, its stupid to spend energy pursuing useless goals.
>
> Also would like to know if there is any way to directly share code between
> two machines running squeak without first having to fileout and then filein?
>
> Awaiting your reply.
>
> Bye.
>
> --
> Mayuresh A Kathe
> Think Different. Think Better.
> mayuresh at vsnl.com