[Squeakfoundation]Network stuff

[Tim Rowledge]

Daniel Vainsencher <danielv at netvision.net.il> wrote:

> Darn, I intended to answer this topic on this thread, but already wrote
> it in the other. In short, I'm for it.
> 
> Anyone objects?
I'm in favour of anything that cleans up the ugliness around filenames,
sockets, streams etc. Now, my understanding is that Flow does a great
deal around this region so perhaps that should be the answer. However,
I also believe (maybe incorrectly) that Flow requires some thread
capability in order to function propelry. Since I can't support threads
on RISC OS and I don't think one can guarantee thread support on
embedded OSs, perhaps I need to stand up for a fallback capability?

Assuming for the moment that Flow is not the best answer for
the immediate future, then these fixups for the older stuff from Mike
are probably a Good Thing. However, reading the comments I get a bit
nervous when I see 'bleeding edge', 'first part of' etc. If Mike is not
claiming that it is ready, perhaps we shouldn't leap too quickly.

I'd really like to see a good answer on all this. Changes to file
handling and sockety stuff are probably some of the most entangled code
around because so many methods make use of them. And _so_ many make poor
use of them....


tim
-- 
Tim Rowledge, tim at sumeru.stanford.edu, http://sumeru.stanford.edu/tim
Useful random insult:- Subtle as a well-thrown brick.