Mailing List is Up

As you all probably know by now, the Swazoo development mailing list at
SourceForge is up and running.  I hope to start up some more discussions
about Swazoo, especially:

- Wiki on Swazoo.  Janko, were you working on this?  I had started on
it, too.
- Ports to other environments.  I'm growing more and more excited about
Squeak every day.  Anybody interested in a port?  I have one class
(StreamingSocket) that will make the port go a lot more smoothly.
- Portability in general.  We should talk about the Dolphin port.  What
needed to change?  How can we isolate the non-portable stuff to make
porting easier?
- OOPSLA.  I won't be able to be there, since my wife and I just had our
first (a son).  I'd love to know what kind of things you OOPSLA-bound
Swazoo-ers are interested in.
- SourceForge... how's it working for people?  Are people more
interested in the raw .st files or VW parcels?
- Should we be looking at SIF instead of chunk?

Comments welcome.  Thanks for letting me subscribe all of you.  Feel
free to unsubscribe if you're not interested anymore.  :)

Janko, I couldn't find Aleksander's email address.  He can subscribe
himself -- or you can send me his address and I'll sign him up.

That's it for now.


Ken Treis
[hidden email]

Hi all,

I'd like to welcome the opening of this mailing list too :)
I hope we will make a Swazoo the standard web server for
Smalltalk world, as soon as possible.

IMHO, our first task is to make Swazoo production ready and
to put him on as much live systems as possible. This will be
very good for "marketing" and "advertising" reasons. This
will then generate more interest for porting Swazoo to other
dialects as a standard web server.

Most of us have a good VW knowledge, so merging all VW Web
stuff and putting Swazoo in front of them is a first thing
to do. Therefore I started with:

- Swazoo-Wiki: putting all good stuff from WikiWorks HTTP
server to Swazoo and putting remaining parts as a resource
to Swazoo. I studied WikiWorks and it seams that this won't
be a problem.

- Swazoo-Aida: I like to replace Aida's HTTP server as soon
as possible with a Swazoo. We need to extend a robustness of
Swazoo a bit before I will be willing to put in on our live
Aida systems.

- Secure Swazoo: OpenSSL interface is VW stuff and it seems
that it will be very difficult to port to other dialects.
So, VW Secure Swazoo is a first thing to do.

- Swazoo Logo :))) and T-shirts for OOPSLA to be loud and
visible ... Jernej, our web designer made logo for SiTALK, a
Slovenian Smalltlak User Group (http://www.sitalk.org), his
logo proposals are on http://www.wikiweb.com/~sitalk/Logo .
But he needs ideas for a logo. Please put your designer
brain part in at least first gear and contribute ideas (on
this mailing list) :)


> - Wiki on Swazoo.  Janko, were you working on this?  I had started on
> it, too.

Ken, are you an author of WikiWorks HTTP part? And please,
send me your work in progress, you probably don't have much
time in these days ;)

> - Ports to other environments.  I'm growing more and more excited about
> Squeak every day.  Anybody interested in a port?  I have one class
> (StreamingSocket) that will make the port go a lot more smoothly.

I tried to port Swazoo to VA, but had problems with sockets.
It seams that this socket stuff will be the most difficult
problem in porting. We need help from socket specialists
from other dialects.

> - Portability in general.  We should talk about the Dolphin port.  What
> needed to change?  How can we isolate the non-portable stuff to make
> porting easier?

We really need Portable Sockets from Internet Client/Server
group here, Does anyone know the status of their work?

> - OOPSLA.  I won't be able to be there, since my wife and I just had our
> first (a son).  I'd love to know what kind of things you OOPSLA-bound
> Swazoo-ers are interested in.

Loud and visible with a working stuff :)) I will have two
demonstrations at OOPSLA about Swazoo-Aida too.


> - SourceForge... how's it working for people?  Are people more
> interested in the raw .st files or VW parcels?

Please let we forget CVS and publish as File Releases to be
visible from a first page. Also, package as .zip or .gz
(better). I think that we MUST publish .st and optionally
parcels, .dat etc. in the same .zip file. This will help
other to look in Swazoo code from text editor, without
installing VW etc.


> - Should we be looking at SIF instead of chunk?

.. or PEPE maybe :) But for a start, a chunk file is more
preferable, IMHO.


> Janko, I couldn't find Aleksander's email address.  He can subscribe
> himself -- or you can send me his address and I'll sign him up.

His e-mail is [hidden email] . I will let him know
about mailing list.



Best regards
Janko

--
Janko Mivsek
Systems Architect
EraNova d.o.o.
Pod hribom 55
SI-1000 Ljubljana
Slovenia
phone: +386 1 5816 232
fax: +386 1 5816 231
[hidden email]
www.eranova.si