re: Network stuff

> I'm in favour of anything that cleans up the ugliness around
> filenames, sockets, streams etc.

	As I recall, Michael's changes are at a higher level, mostly for
"session protocol" support (given streams already, how to speak HTTP,
etc.). They do continue to use the current low-level external-resource
support, though. Flow does change that lower-level support, so there
would need to be some further modification of Michael's work in a system
in which, e.g., Flow is the only low-level external-resource support
available.

> I also believe (maybe incorrectly) that Flow requires some thread
> capability in order to function propelry.

	That's correct currently. One could modify it so that weren't the case,
but I have no interest in that myself.

> Since I can't support threads on RISC OS...

	What's the ETA for the RISC-OS POSIX threads project?

> ...and I don't think one can guarantee thread support on embedded
> OSs...

	Some do provide that support. I don't think it's appropriate to lump
them all together as "providing no guarantee". Can you cite some
specific examples of embedded operating systems that don't provide
thread support?

	I think Michael's changes make sense now, regardless of the Flow
schedule.

	I also think all the packages we've mentioned so far should appear
optional to the user. If it seems like something will "rot" because it
is merely available from SqueakMap and not in a release snapshot, then
there's something wrong with the SqueakMap system (and we should fix
it). None of this stuff should be in a release snapshot.


	thanks,

-C

--
Craig Latta
http://netjam.org/resume
[email protected]
Smalltalkers do: [:it | All with: Class, (And love: it)]
From [email protected] Mon May 05 23:12:34 2003
Return-Path: <[email protected]>
Delivered-To: [email protected]
Received: (qmail 29088 invoked from network); 5 May 2003 23:12:33 -0000
Received: from mail.gmx.net (213.165.64.20)
  by mail.theinternetone.net with SMTP; 5 May 2003 23:12:33 -0000
Received: (qmail 7321 invoked by uid 65534); 5 May 2003 23:12:33 -0000
Received: from pD9533EAB.dip.t-dialin.net (EHLO atlantis) (217.83.62.171)
  by mail.gmx.net (mp017-rz3) with SMTP; 06 May 2003 01:12:33 +0200
From: "Andreas Raab" <[email protected]>
To: "'Discussing the Squeak Foundation'"
	<[email protected]>
Subject: RE: [Squeakfoundation]re: Network stuff
Date: Tue, 6 May 2003 01:12:18 +0200
Message-ID: <000b01c3135b$c6c6e0e0$8ef7fea9@atlantis>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4510
In-Reply-To: <[email protected]>
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Importance: Normal
X-BeenThere: [email protected]
X-Mailman-Version: 2.1
Precedence: list
Reply-To: Discussing the Squeak Foundation
	<[email protected]>
List-Id: Discussing the Squeak Foundation
 <squeakfoundation.lists.squeakfoundation.org>
List-Unsubscribe: <http://lists.squeakfoundation.org/listinfo/squeakfoundation>,
	<mailto:[email protected]?subject=unsubscribe>
List-Archive: <http://lnx-12.ams-2.theinternetone.net/pipermail/squeakfoundation>
List-Post: <mailto:[email protected]>
List-Help: <mailto:[email protected]?subject=help>
List-Subscribe: <http://lists.squeakfoundation.org/listinfo/squeakfoundation>,
	<mailto:[email protected]?subject=subscribe>
X-List-Received-Date: Mon, 05 May 2003 23:12:34 -0000

> 	I also think all the packages we've mentioned so far=20
> should appear optional to the user. If it seems like something
> will "rot" because it is merely available from SqueakMap and
> not in a release snapshot, then there's something wrong with
> the SqueakMap system (and we should fix it).

These changes are somewhat "special" in such that we're talking about
rewriting these things rather than merely adding something. In other =
words:
In this particular case any evolution that goes on within Squeak renders =
the
changes done questionable (if not entirely unusable). Think, for =
example,
about the recent discussions at Squeak-Dev about using progress =
indicator,
#confirm: and friends - many of those are used exactly wrong in the
networking code and in this sense, as soon as someone starts to touch =
these
places, the stuff that's up at SqueakMap really does "rot". BTW, the =
issue
of notifiers popping up in background threads was the latest reason why =
I
wanted this stuff fixed ;-)

Cheers,
  - Andreas