Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

release v2.4.3.1 #66

Merged
merged 79 commits into from
Jan 15, 2015
Merged

release v2.4.3.1 #66

merged 79 commits into from
Jan 15, 2015

Conversation

dalehenrich
Copy link
Member

  • @HeSe port of Zinc Web Sockets to GsDevKit.
  • Use GsDevKit/Cryptography project.
  • add ZnGemServer for GsDevKit/gsApplicationTools Gem Server support.
    • ZnGemServer-based tests for Web Sockets, HTTP and REST.
    • ZnGemServer support for logging to Transcript or Object Log:
      • logToObjectLog
      • logToTranscript
    • plus control over what gets logged:
      • logErrorsOnly
      • logEverything
    • ZnGemServer support for the following ZnServer options:
      • authenticator
      • bindingAddress
      • debugMode
      • delegate
      • maximumEntitySize
      • reader
      • route
      • serverUrl
      • useGzipCompressionAndChunking
  • Improved continuation support with ZnTransactionSafeManagingMultiThreadedServer.
    • ZnTransactionSafeManagingMultiThreadedServer is the default Server class for GsDevKit.
    • continuations are snapped off for ZnServer infrastructure errors, Halt, and Breakpoints. This support does not interfere with the continuation support provided for Seaside. Instead it provides you with the the equivalent functionality for non-Seaside servers like Web Socket, REST or simple HTTP servers. Note that remote Breakpoints should not be used until 3.2.4 or later.
    • bugfixes and improved continuation support for SocketStream and SocketStreamSocket classes.
    • TransientValue and TrasientStackValue class used in strategic locations to prevent GsSocket and GsProcess instances from being committed.
  • fix potential infinite loop on accept error in SocketStreamSocket (d8b7082), by checking for error from underLying socket accept call
  • additional Zinc bug fixes:

From PR #70:

  • ZnManagingMultiThreadedServer is used by default for the classic pre-GemServer ZnServers
  • ZnTransactionSafeManagingMultiThreadedServer: shoehorn in object log logging for ZnGemServer object logging
  • ZnGemServerManagingMultiThreadedServer major refactoring of the ZnServer methods to take full advantage of ZnNewGemServer

Sorry, something went wrong.

…roject and add backin into CI group, since the project should now load without errors
…or all required projects for zinc ... may need to pull in tests vi CI group
….. will be available soonish on the glass master branch
…erver-Tools, a new package which holds ZnServerStarter class needed by web socket tests ...
- always snap off continuation when an error event occurs
- add some error handling a bit higher up the zn stack ...
  to catch application errors as well ... might be able to
  continue processing without passing error ... still passing at
  the moment...
- ZnTranscriptLogger for all ZnGemServer guys ... might want to
  make this easier to customize
…default errors are logged to transcript and continuation commmited to object log....
…use ZnObjectLogLogger ... practical to debug ZnGemServer using object log logging and continuations
…secure sockets (Zodiac) ... not supported in GemStone at the moment
… on debugMode: for all of the tests useing GemServer ... if there is a problem with the test passing we are going to want to look at the object log ...
… the exception ... debugMode doesn't quite appy to GemStone ... need different granularity I think ... GsPharo 0.9.2 needs to be used
…o understand the odd 30 second delay for the chat delegate
… log an error: and handleError: for GemStone so we make sure that all errors make it to the log (object log and continuation) AND the gem file .... add gobs of log helper methods to ZnGemServer ... control logging method and filter and whether or not continuations are created for errors from ZnGemServer
…rveConnectionOn: and ZnMultiThreadedServer>>executeRequestResponseLoopOn:
…the object log...refactor REST tests to allow for testing using remote ZnGemServer and add persistence to ZnExampleStorageRestServerDelegate ... a bit of house cleaning in ZnGemServer
…etStreamSocket would lead to an infinite loop creating processes and then running out of memory ... Fix Rest test error ... only pass exceptions in debugMode for ZnServer
@dalehenrich dalehenrich changed the title merge Issue 58 release 2.4.3.1 Dec 15, 2014
@dalehenrich dalehenrich changed the title release 2.4.3.1 release v2.4.3.1 Dec 15, 2014
…erver, but it is natural for ZnGemServer to refer to ports ... a bow to compat
…ing ZnNewGemServer that is married with ZnGemServerManagingMultiThreadedServer which is a refactored ZnTransactionSafeManagingMultiThreadedServer/ZnManagingMultiThreadedServer that replaces all of the error handling with gemServer:* calls ... create interfact to delegates so that ZnGemServerManagingMultiThreadedServer can be used with any existing delegates, although by default there are no transactions being performed, but the handleRequest:gemServer: method can changed to add transactions ... no tests for the new boys ... yet
…e tests can be run against an interactive gem server running in second tODE environmnent ... 19 run, 9 passes, 0 expected defects, 10 failures, 0 errors, 0 unexpected passes .... so blatant server-side errors have been cleaned up
… handling to the handler up the stack ... logging and proper error response handling is already defined ...revise comments in delegate handleRequest:gemServer: methods
…m failures .... all tests run clean in my 3.2.2 dev image
merge Issue 69 into Issue 58
dalehenrich added a commit that referenced this pull request Jan 15, 2015
@dalehenrich dalehenrich merged commit 452f043 into gs_master Jan 15, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant