Swazoo 2.1 Release NotesChanges from 2.0 (aug07): --- On: 12/31/2007 17:38:34.000
- beta3, synced with Squeak Swazoo-2.1.beta3
- SwazooServer swazoVersion and not version, to avoid method conflicts on Squeak. --- On: 12/31/2007 13:31:29.000
Swazoo-Extensions cleanup to have only extensions
- class HTTPString to package Swazoo-HTTP
- namespace Swazoo to package Swazo-Core
- class SwazooCompiler to Swazoo-Resources --- On: 12/31/2007 12:57:50.000
- Swazoo bundle properties: updated version, comment
- Url encoded POST support rechecked, test added
- HTTPost urlencodedDataFrom: encode/decode both name and value in pairs --- On: 12/29/2007 0:09:27.000
- SwazooServer startOn: starts a demo site on that port and all interfaces, any host, and creates demo site if no site yet
- SwazooServer demoStart starts on 8888 but all interfaces!
- SwazooServer addSite: allows more preciselly host:ip:port
combinations
- SwazooServerTest with additional tests for sites --- On: 12/28/2007 11:02:32.000
-HTTPConnection getAndDispachMessages: back 100ms delay before connection close --- On: 12/27/2007 21:51:57.000
- no more diagnostics in HTTPConnection
- package Swazoo-Extensions except Swazoo-Compatibility --- On: 12/20/2007 13:43:48.000
- Connection close for all responses (streamed too). That is moved in
HTTPConnection to #produceResponseTo: from #nextPutMessage:
- HTTPConnection keepAliveTimeout
- HTTPRequest better pirntString with user agent, connection, 1.0
- HTTPHeaders printOn: for easier debugging --- On: 12/20/2007 9:59:34.000
HTTPConnection keepAliveTimeout check introduced --- On: 12/19/2007 11:47:21.000
HTTPResponse printContentLength adds to headers too, for easier debugging --- On: 12/19/2007 0:08:38.000
Connection: Keep-alive, if in request then put in response too, even for HTTP/1.1 --- On: 12/18/2007 14:13:47.000
- Streaming in case of HTTP/1.0 protocol - not chunked, if length is known, stream but not chunked.
- HttpStreamedResponse, HTTPResponse
- HTTPConnection close after every HTTP/1.0 response, regardless of Keep-alive. --- On: 12/18/2007 10:59:39.000
- SwazooTask connection to backlink to a parent connection
- HTTPMessage task instead of parent. --- On: 12/18/2007 10:22:05.000
- HTTPRequest, HTTPRequestLine isHttp10, isHttp11. --- On: 12/17/2007 16:52:54.000
Finally solved "broken pipe" problem?
- HTTPResponse produceResponseFor waits until all streamed data send! Until now it just returned!
- HTTPStreamed response waitClose on a semaphore until all data is streamed out
- SwazooBuffer buffer size to 8K
- tests: TCPAnalyser to help analysing net problems --- On: 12/14/2007 21:30:39.000
Broken pipe problem caused by prematurelly closed socket because of bad request comming in the middle of sending? IT seems that on VW sending is still in action when we sent last packet, so immediatelly closing a connection after bad request broke a "pipe".
50ms delay is introduced after any such error in HTTPConnection interact and before connection is forced to close.
Also there is a read from empty socket problem on VW which is caused from some clients (sending FIN in last packet, why?) If that happens, a connection is closed (again after 50ms) without sending back a 400 bad request. Maybe this will help ? --- On: 12/07/2007 11:14:05.000
- #version moved to SwazooServer class, previously was in HTTPServer class
- version to Swazoo 2.1 --- On: 11/28/2007 14:42:34.000
- no more connection close after 302 redirect (HTTPConnection nextPutResponse:toRequest:) --- On: 11/15/2007 13:33:33.000
- SiteIdentifier portMatch: if host is star then any port is ok.
- SwazooServer watchdog instvar added, just that for now
PATCH:
- HttpConnection produceResponse closes connection after every non-GET, this solves 200 bad request error after two consecutive POSTs, but it is really a hack and original reason must be found! --- On: 10/29/2007 13:16:09.000
-SwazooServer startOn: port (it will run on al iterfaces, ignoring host)
-SwazooBuffer to 64K --- On: 10/28/2007 9:56:32.000
SwazooBuffer to 64K --- On: 09/28/2007 23:04:11.000
- HTTPResponse printContentLengthOn:
- ContentTypeField valuesAsStringOn: works now
- HTTPRequestTest multipart header test added --- On: 09/06/2007 14:29:03.000
- auto-restart of Swazoo sites, which were running before shutdown
- reorg and remove unneeded methods in Site
- Swazooserver demoStart/stop ''swazoodemo'' site
- SwazooServer watchdog instvar added
- SwazooSocket/Stream/Buffer moved to Swazoo-HTTP --- On: 08/17/2007 22:23:40.000
- asSpTimestamp removed from Timestamp
|