0.9.59 for review

> Thanks for this important work!
>
> At 12:02 PM 3/27/2002 +0100, Janko Mivsek wrote:
>
>> 3. Load order, prerequisites, proper extensions/overrides
>>
>> - Swazoo-SSL wants OpenSSL, which wants DLLCC parcel to be loaded
>> - Swazoo-VisualWorks wants Swazoo-Core
>> - Swazoo-Tests wants Swazoo-Core and SUnit
>>
>> We need to test that on vanilla image to see if it really works
>> correctly. I had quite some problems and they are solved on my local
>> Store now.
>
>
> I commented out the initInterface message send in OpenSSLBase
> class>>initialize method to allow the package to be loaded without the
> supporting DLL in place. I've published a new version of the OpenSSL
> package and the Swazoo bundle (0.9.60) with this change.
>
> I believe that lazy initialization will handle this properly anyway,
> but I have not yet tested on a platform with the DLL in place.

>
>
>> Best regards
>> Janko
>
>
> Thanks again!
>
>
> -Mark Schwenk
>  WellThot Inc.
>
>
>

> Hi all,
>
> I just published another version where I added/changed:
>
> 1. Consistent start/stop
>
> - Added start/stop of Sites. Site start will create and start
> appropriate HTTP
>   servers, if they are not already created with some other running site.
> Site stop will
>   stop and remove all HTTP servers not used for other sites.
> - Removing of a Site will stop it first in order to properly close all
> sockets.
> - SiteRegistry singletron initialize will first remove all sites, this
> will stop
>   all sites and HTTP servers first in order to close all TCP sockets.
> - SiteRegistry configureFrom: 'sites.cnf' will first remove all existent
> Sites!
> - SiteRegistry singleton start will start all Sites
> - SiteRegistry singleton stop will stop all Sites
>
> 2. Multihomed host support (hosts with more than one ip)
>
> - suport for virtual sites previously worked only on one ip
> (IPSocketAddress thisHost) and
>   ip part of SiteIdentifier was ignored. This is now put in full
> functionality.
>   HTTServers will start on ip defined in SiteIdentifiers.
>
> 3. Load order, prerequisites, proper extensions/overrides
>
> - Swazoo-SSL wants OpenSSL, which wants DLLCC parcel to be loaded
> - Swazoo-VisualWorks wants Swazoo-Core
> - Swazoo-Tests wants Swazoo-Core and SUnit
>
> We need to test that on vanilla image to see if it really works
> correctly. I had quite some problems and they are solved on my local
> Store now.
>
> 4. Some minor fixes of previous release
>
> - 0.9.58 tests passed, yes, but Swazoo didn't actually work ... Problem was
>   in setting a timestamp in HTTPConnection (self setTimestamp instead of
>   self timestamp: Timestamp now)
>
> 5. Ken, keeper process forking in HTTPConnection getAndDispatchMessages
> is commented out because it causes a creation of big number of
> processes. We need to find a better way for that. Maybe one keeper
> process per connection and sending it an events like connection closed,
> timeout, change of state (idle, receiving, processing etc).
>
> Tests are a bit changed, they pass correctly. Swazoo live configuring,
> reconfiguring, starting, restarting, stoping, initializing ... in all
> combinations I could imagine didn't show any problems like remaining
> open sockets, address already in use or similar problems.
>
> For all please take a bit time, load it in a plain vannila image, (be
> sure that SSL libraries and certificates are in place) and test it as
> much as possible. You can skip SSL with loading only Swazoo-Core package
> (which should load Swazoo-VisualWorks automatically)
>
>
> Best regards
> Janko
>
>
> _______________________________________________
> Swazoo-devel mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/swazoo-devel
>
>