-(name 'Seaside-GemStone-ServiceExamples-dkh.25' message 'checkpoint- tweak the seaside component- start new seaside description section in docs- add convenience script for bringing up object log- add zinc script (maybe get rid of this one?)' id 'd5635769-aa12-4ffe-8195-21a07636cedf' date '06/12/2014' time '12:25:47' author 'dkh' ancestors ((name 'Seaside-GemStone-ServiceExamples-dkh.24' message 'checkpoint ... needed a little transaction in the time in london guy ...' id '8af7016e-8d39-423b-b85c-2c8b3d7b9254' date '06/10/2014' time '08:12:28' author 'dkh' ancestors ((name 'Seaside-GemStone-ServiceExamples-dkh.23' message 'finally get example running again after all of the recent rewriting ...' id '730ae9ae-cea9-4faa-93ef-9ba0b5887ee6' date '06/09/2014' time '20:43:28' author 'dkh' ancestors ((name 'Seaside-GemStone-ServiceExamples-dkh.22' message 'fix WAGemStoneServiceExampleTimeInLondon class>>url:' id '61851330-34d0-4ab0-b8ac-5fd9653484f8' date '06/09/2014' time '18:54:25' author 'dkh' ancestors ((name 'Seaside-GemStone-ServiceExamples-dkh.21' message 'Decided to not use WAGemStoneServiceTask as is:- The api is a bit awkward for what I want to illustrate in the example and in the off chance that folks are using WAGemStoneServiceTask in production, I basically copied WAGemStoneServiceTask to WAGemStoneServiceExampleTask and then proceeded to massage it to my will- in concert with that I am now using WAGemStoneServiceExampleVM for the example...- adjusted the serviceVM script to match- finally rewrote the example Seaside component from scratch to match' id 'a107f958-1ed3-4706-90a7-61977928e50d' date '06/09/2014' time '12:47:22' author 'dkh' ancestors ((name 'Seaside-GemStone-ServiceExamples-dkh.20' message 'add WAGemStoneServiceExampleTimeInLondon .. application task class' id 'd254d00e-b015-40dc-8c7d-9b6883fc2a18' date '06/08/2014' time '17:14:27' author 'dkh' ancestors ((name 'Seaside-GemStone-ServiceExamples-dkh.19' message 'simplification of ServiceVM example without breaking existing stuff- build new vm hierarchy under WAGemStoneAbstractServiceVM which is basically WAGemStoneServiceVMTask reafactored to support multiple subclasses - new classes WAGemStoneServiceExampleVM (for old example) and WAGemStoneServiceVM (for new example which will be built upon Nick''s WAGemStoneServiceTask; block-based and much simpler- restore Seaside-GemStone-ServiceTask-NickAger.20 - implementation of WAGemStoneServiceVMTask left alone in case folks are using it in production ... evenutally they should convert and until then ..' id '109fbd95-00d1-4425-bb99-cc20816b93a1' date '06/08/2014' time '14:26:14' author 'dkh' ancestors ((name 'Seaside-GemStone-ServiceExamples-dkh.18' message 'remove comments ... only needed for the docs, methinks' id '3f9b0cbe-e755-4581-b858-f88989d3810f' date '06/08/2014' time '11:48:56' author 'dkh' ancestors ((name 'Seaside-GemStone-ServiceExamples-dkh.17' message 'refactoring ...' id 'af8988bf-2199-4100-a179-b2c0937b67e8' date '06/08/2014' time '10:46:35' author 'dkh' ancestors ((name 'Seaside-GemStone-ServiceExamples-dkh.16' message 'add comments to render method (WAGemStoneInteractiveServiceExample>>renderContentOn:) to highlightstate transitions ... ad webServer script code ...' id 'c5e6bd00-ad17-4765-800b-f7ccdf3ce9bf' date '06/07/2014' time '18:21:23' author 'dkh' ancestors ((name 'Seaside-GemStone-ServiceExamples-dkh.15' message 'start documenting the Seaside loop' id '1a0329c3-f8a1-439f-a91d-b28edf3a1028' date '06/07/2014' time '18:07:42' author 'dkh' ancestors ((name 'Seaside-GemStone-ServiceExamples-dkh.14' message 'more renaming and more docs ...' id '1d6b9060-ef92-45d6-acbb-9ee72fdf3215' date '06/07/2014' time '13:04:42' author 'dkh' ancestors ((name 'Seaside-GemStone-ServiceExamples-dkh.13' message 'rename WAGemStoneServiceTask to WAGemStoneServiceExampleWorkUnit ... edit readme and scripts to match' id '52545f08-6b4f-488e-809a-6666449e904d' date '06/07/2014' time '09:45:34' author 'dkh' ancestors ((name 'Seaside-GemStone-ServiceExamples-dkh.12' message 'remove and consolidate ... drop the restful stuff in favor of tode-base scripts ... example is fuly functional and README is partially finished ... need to complete documentation and rework code/scripts in support of the documentation' id '824d802f-7a51-4171-8b2c-69c567efeb60' date '06/07/2014' time '09:32:43' author 'dkh' ancestors ((name 'Seaside-GemStone-ServiceExamples-dkh.11' message 'WAServiceVMGem class is used to treat service vm as a WAGemStoneRunSmalltalkServer server ... service vm starts up ... WAGemStoneRestfulServiceHandler not compatible with with the Seaside3.1 restful implementation' id '144ae7fa-4333-4222-a4e9-ec9e6935d10c' date '06/06/2014' time '22:01:52' author 'dkh' ancestors ((name 'Seaside-GemStone-ServiceExamples-DaleHenrichs.10' message '- renamed some classes- cleaned things up a bit- tracking inProcess tasks- vm restart logic - handling 6 tasks per second before target begins falling behind)...- RESTful api runs at 500 requests/second...' id '7c10a623-9e01-4591-9fdc-c33d914b111e' date '08/25/2010' time '13:37:50' author 'DaleHenrichs' ancestors ((name 'Seaside-GemStone-ServiceExamples-DaleHenrichs.9' message '- a little more data collection to find the tipping point ... when we start falling behind, because the target http site can''t handle the load (bibliocello looks like it can handle about 2 directory requests/second (seaside repos) ... should look into this...' id '5d9a3373-bc7b-42e7-beb7-600f9f3469ea' date '08/24/2010' time '21:19:20' author 'DaleHenrichs' ancestors ((name 'Seaside-GemStone-ServiceExamples-DaleHenrichs.8' message '- stands up to siege pretty well ...- when starting up a vm or at other times, it is necessary to scan the log and reschedule all workunits that are not finished' id 'e8649fa4-a4b6-456b-8107-04213859b847' date '08/24/2010' time '18:08:47' author 'DaleHenrichs' ancestors ((name 'Seaside-GemStone-ServiceExamples-DaleHenrichs.7' message '- added a RESTful API for service, so that siege can be used to load up server' id 'c9f176f8-5e82-4bc4-8cda-938ac0a79fe1' date '08/24/2010' time '15:31:17' author 'DaleHenrichs' ancestors ((name 'Seaside-GemStone-ServiceExamples-DaleHenrichs.6' message '- pretty close to final form ... passes jcrawler test ...' id '193f996c-cb5e-431f-adbb-e1b1779cc990' date '08/24/2010' time '09:57:23' author 'DaleHenrichs' ancestors ((name 'Seaside-GemStone-ServiceExamples-DaleHenrichs.5' message '- would like to fork processing of workunits ...' id '959f9068-4101-4e48-8ee3-167299cf8bed' date '08/24/2010' time '03:54:47' author 'DaleHenrichs' ancestors ((name 'Seaside-GemStone-ServiceExamples-DaleHenrichs.4' message '- running on short 200ms cycle... random delays for step2' id '4c6533d4-e97d-4ea2-9d60-dacf7bbce0c3' date '08/24/2010' time '03:27:09' author 'DaleHenrichs' ancestors ((name 'Seaside-GemStone-ServiceExamples-DaleHenrichs.3' message '- blocking and nonblocking options for waiting for workunit to be performed...' id 'a478180f-2801-427a-a69b-77ead72d7e72' date '08/24/2010' time '01:03:31' author 'DaleHenrichs' ancestors ((name 'Seaside-GemStone-ServiceExamples-DaleHenrichs.2' message '- basic functionality' id '68d35047-42e1-4ab2-afc8-7969a2463454' date '08/24/2010' time '00:29:23' author 'DaleHenrichs' ancestors ((name 'Seaside-GemStone-ServiceExamples-DaleHenrichs.1' message '- just getting started' id 'aa7f02fc-479a-422c-8361-cb9087253ce5' date '08/23/2010' time '17:43:59' author 'DaleHenrichs' ancestors () stepChildren ())) stepChildren ())) stepChildren ())) stepChildren ())) stepChildren ())) stepChildren ())) stepChildren ())) stepChildren ())) stepChildren ())) stepChildren ())) stepChildren ())) stepChildren ())) stepChildren ())) stepChildren ())) stepChildren ())) stepChildren ())) stepChildren ())) stepChildren ())) stepChildren ())) stepChildren ())) stepChildren ())) stepChildren ())) stepChildren ())) stepChildren ())) stepChildren ())
0 commit comments