[Glass] Zinc and REST on 3.1.0.X

[Ken Treis]

Hi Dale,

I haven't played with the git stuff for a while. I need to get back into that.

I think the main changes that I haven't pushed to Github are:

1. Adding SpSocketError to the pile of exceptions handled by the read/writeRequestSafely: methods
2. Increasing the maximumNumberOfDictionaryEntries.

You wouldn't have to merge #2. Our app needed it because we have some big forms, but unfortunately there was no clean way to override the default (say in ZnConstants) without changing the code.

Other than that, there are some streaming packages. We're using these, together with another hacked backport of WAComboRequest, to send results to the browser in chunks. There's no clean way to handle transaction failure when you're doing that, so we only use it in combination with an unlock and abort. Again, no need to merge those.

I also started to shuffle some code around to better match what Sven has done upstream, but I didn't get very far on that project either. Pesky deadlines...

--
Ken Treis
Miriam Technologies, Inc.
(866) 652-2040 x221

On Jul 2, 2013, at 9:25 AM, Dale K. Henrichs wrote:

> Ken,
> 
> Does your hacked version match the version that is up on github[1]?
> 
> I just took a quick look at the Zinc test failures for 3.1 and they are the familiar fork:at: issue, so I was planning on merging the changes that you'd made on github, but if there are additional hacks not on github, I probably should include them as well ... 
> 
> Sebastian, the 3.1 test failures in the current glassdb version are pretty fundamental so I'd recommend going with Ken's port until I can get his edits integrated...
> 
> Dale
> 
> [1] https://github.com/ktreis/zinc
> 
> From: "Ken Treis" <ken at miriamtech.com>
> To: "Sebastian Heidbrink" <sebastian_heidbrink at yahoo.de>
> Cc: glass at lists.gemtalksystems.com
> Sent: Tuesday, July 2, 2013 7:35:19 AM
> Subject: Re: [Glass] Zinc and REST on 3.1.0.X
> 
> Hi Sebastian,
> 
> We're using Zinc on 3.1.0.1 (hopefully upgrading to 3.1.0.4 this week). I don't remember everything I had to do to get it working, but I know it involved at least:
> 
> * Using a 3.1.0.X port of Zinc. Feel free to use my hacked versions here:
> 
> 	http://mc.miriamtech.com/zinc
> 
> * Configuring WAGemStoneRunSeasideGems to use Zinc adaptors. Something like:
> 
> 	WAGemStoneRunSeasideGems default
> 		name: 'Zinc';
> 		adaptorClass: WAGsZincAdaptor;
> 		ports: #(9001 9002 9003).
> 
> Hope that helps,
> 
> --
> Ken Treis
> Miriam Technologies, Inc.
> (866) 652-2040 x221
> 
> On Jul 1, 2013, at 2:01 PM, Sebastian Heidbrink wrote:
> 
> Hi All!
> 
> I finally started to port one of my prototypes to Gemstone/Web.
> 
> My Pharo portotype uses Seaside and Seaside-REST and Amber as a frontend.
> 
> I used the most current 3.1.0.4 version of Gemstone and I was wondering if somebody can give me some tips on how to startup Zinc.
> I do not really need Seaside and I would prefer to use Zinc-Rest for my kind of application....
> 
> I know that there are test failing currently but I'm not too sure if my loaded code base is the right one anyways.
> 
> Is there somebody how has at least managed to start a Zinc Server on 3.1.0.X and if so,... what did you load and how do you start it ;-)
> 
> Thanks for you help!
> Sebastian
> 
> _______________________________________________
> Glass mailing list
> Glass at lists.gemtalksystems.com
> http://lists.gemtalksystems.com/mailman/listinfo/glass
> 
> 
> _______________________________________________
> Glass mailing list
> Glass at lists.gemtalksystems.com
> http://lists.gemtalksystems.com/mailman/listinfo/glass

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gemtalksystems.com/mailman/private/glass/attachments/20130702/4ead0761/attachment.html>