Any progress?
I use Flow everyday, and I'm tired of modifying my projects to use Socket before publishing them. Last weekend started working on a VNC client, and I don't really want to spend time making it work with Socket.
I love Flow, and I already said how much I'd like to see it integrated into the official release. But I'll be happy if at least NetStreams make it.
Is it possible (and reasonable) to modify the ExternalStreams and ExternalResources in order to load them in an image with the standard Streams? If we can get NetStreams into the 3.3a image, the next step will be removing Socket and refactoring FTPSocket, HTTPSocket and SMTPSocket into FTPClient, HTTPClient, and SMTPClient.
What do you think? If you like the idea, I offer my spare time for anything you need to get this done.
Peace, Luciano.-
===== http://community.corest.com/~luciano CCB0 B2B0 BCCB 8178 CA8B 4C08 AE9B D2F2 E9CC E897
__________________________________________________ Do You Yahoo!? Yahoo! Health - Feel better, live better http://health.yahoo.com
Hi Luciano--
Any progress?
Yes! I'm just about done packaging Flow 2 alpha for release. It's tricky, because there are several places where file-in ordering is critical. I got tired of editing fileouts manually in a text editor, so I'm actually dividing the release into as many change sets as necessary to accomodate the sequencing.
Because there are so many change sets involved (29 so far, there used to be four), I've created an "installable archive" format. This enables the release to take the form of a single file. It's basically a normal ZIP archive of all the files, with a Smalltalk expression at the beginning which does the right thing with the ZIP bits after it. I think it'll work pretty well.
Is it possible (and reasonable) to modify the ExternalStreams and ExternalResources in order to load them in an image with the standard Streams?
It's doable, but a lot of work, and I'd rather not do it, since Flow 2a installs without interfering with the old streams/sockets. I'm still hoping to get people using NetStreams via Flow 2a, and then later just remove the old streams/sockets.
...the next step will be removing Socket and refactoring FTPSocket, HTTPSocket and SMTPSocket into FTPClient, HTTPClient, and SMTPClient.
Yeah, that part will be fun. :) I think we'll be able to start on that this week.
...I offer my spare time for anything you need to get this done.
Thanks! After I get Flow 2a out, I think we should just make a list of all the internet protocols we want to use, then divide them up and implement them.
Thanks for your patience... I'm fitting coding in between unexpected summer travelling. :) I think it'll be another few days (hopefully before I travel again on Thursday, to DEFCON).
-C
-- Craig Latta improvisational musical informaticist craig@netjam.org www.netjam.org Smalltalkers do: [:it | All with: Class, (And love: it)]
--- Craig Latta craig.latta@netjam.org wrote:
I'm just about done packaging Flow 2 alpha for release.
That's wonderful news! Thanks!
I'm still hoping to get people using NetStreams via Flow 2a, and then later just remove the old streams/sockets.
Do you think there's a chance to get this into the 3.3a image? Or do you want to remove the old Stream hierarchy before doing that? I think refactoring the image to remove all dependencies on the old Streams is a non-trivial task, and would be easier once Flow is incorporated into the official release.
I think it'll be another few days (hopefully before I travel again on Thursday, to DEFCON.
Cool! If you go to BlackHat, check out Maximilano Caceres' talk on "Syscall Proxying-Simulating Remote Execution". I have a Squeak implementation, with shellcodes for Linux and Open/Free/NetBSD (x86). It's part of a bigger project (my army of mobile agents). I'll release this soon, probably next month.
Cheers, Luciano.-
===== http://community.corest.com/~luciano CCB0 B2B0 BCCB 8178 CA8B 4C08 AE9B D2F2 E9CC E897
__________________________________________________ Do You Yahoo!? Yahoo! Health - Feel better, live better http://health.yahoo.com
That's wonderful news! Thanks!
Sure! :)
I'm still hoping to get people using NetStreams via Flow 2a, and then later just remove the old streams/sockets.
Do you think there's a chance to get this into the 3.3a image?
Certainly. Flow 2a and the old Stream hierarchy co-exist; people will be able to use both. I'll actually be releasing two versions concurrently: Flow 2a1, which installs into Squeak 3.2f images, and Flow 2a2, which installs into Squeak 3.3a (current) images.
I think refactoring the image to remove all dependencies on the old Streams is a non-trivial task, and would be easier once Flow is incorporated into the official release.
I agree, and I hope that's what happens.
If you go to BlackHat, check out Maximilano Caceres' talk on "Syscall Proxying-Simulating Remote Execution". I have a Squeak implementation, with shellcodes for Linux and Open/Free/NetBSD (x86). It's part of a bigger project (my army of mobile agents). I'll release this soon, probably next month.
Wow, neat!
thanks again,
-C
-- Craig Latta improvisational musical informaticist craig@netjam.org www.netjam.org Smalltalkers do: [:it | All with: Class, (And love: it)]
Hi--
Well, I'm stuck. I can't get OpenBSD (3.1) to make a Flow.so that runs. Specifically, the compile-time linker seems to have prepended a leading underscore to all the pthreads function calls, then the dynamic linker can't resolve them. I can't figure out how to keep those underscores out. I've posted a question to comp.unix.bsd.openbsd.misc asking about this.
Just curious... what platforms are people on? I might just release Flow 2a anyway, even though I haven't tested it to my satisfaction.
-C
-- Craig Latta improvisational musical informaticist craig@netjam.org www.netjam.org Smalltalkers do: [:it | All with: Class, (And love: it)]
flow@lists.squeakfoundation.org
-
Craig Latta -
Luciano Notarfrancesco -
Luciano Notarfrancesco