GemStone/S 64 Bit 3.0.0Beta3 available
Locked
GemStone/S 64 Bit 3.0.0Beta3 available
 
|
Yesterday we announced the availability of GemStone 3.0.0Beta3. From the
announcement email: We have released GemStone/S 64 Bit 3.0.0Beta3. This is the third in a series of beta releases previewing the next generation of the GemStone/S Smalltalk object server. Archives of this release may be downloaded from the following URL: ftp://ftp.gemstone.com/pub/GemStone64/3.0.0Beta3/ Revised installation guides are available at the following URL: http://community.gemstone.com/display/GSS6 /GemStoneS+64+bit+3.0+Beta+Documentation Seaside3.0 is functional on this release. There are a number of tests that don't pass and the engineering team is continuing to fix bugs in the server. If you want to kick the tires on 3.0 and Seaside3.0 then I encourage you to take it for a spin. If you run into problems with GemTools or Seaside or the base image code, please submit a glassdb issue and I will route it to the engineering team if it is a base bug. I also encourage you to subscribe to the GemStoneBeta mailing list where discussions and further server beta related announcements will be made. To subscribe, send an e-mail with the single word "subscribe" (without quotes) in the subject line or body of the message to the list administrative address, [hidden email]. To work with GLASS and Seaside3.0 in GemStone3.0 you will need to update to the latest GLASS 1.0-beta.8.6 and use version 3.0.3.1 of Seaside. Both of these versions are under active development so it is possible that there will be load/update issues over time. so it is a good idea to backup before updating. Use the GemTools menu to update GLASS and use the following expression to load/update Seaside3.0: Gofer new squeaksource: 'Seaside30'; package: 'ConfigurationOfSeaside30'; package: 'ConfigurationOfGrease'; load. GsDeployer deploy: [ Gofer project load: 'Seaside30' version: '3.0.3.1' group: 'ALL'. ] Note that I'm using GsDeployer class>deploy: instead of MCPlatformSupport class>>commitOnAlmostOutOfMemoryDuring:. GsDeployer class>deploy: does a commitOnAlmostOutOfMemoryDuring:, handles Warnings by dumping the description to the transcript, turns off autoMigrate, executes the block and then does a bulk migrate of instances for all classes changed during update ... should result in way faster upgrades and migrations... For the beta, there is no supported upgrade path between beta releases, so don't do anything important in the beta. Also, for this beta, there is no upgrade path from 2.4.4.1 to 3.0...that will be forthcoming in a future release. Dale |
Re: GemStone/S 64 Bit 3.0.0Beta3 available
|
|
Dale,
On 04.02.2011, at 20:14, Dale Henrichs wrote: I also encourage you to subscribe to the GemStoneBeta mailing list where discussions and further server beta related announcements will be made. To subscribe, send an e-mail with the single word "subscribe" (without quotes) in the subject line or body of the message to the list administrative address, [hidden email]. if you subscribe to the list you get mailman mail with a bogus link in the mail text. It has a subscription link that points to mailman2.vmware.com. This hostname does not exist (not even in any vmware dns server). Probabily you can forward this to the person in charge. Norbert |
Re: GemStone/S 64 Bit 3.0.0Beta3 available
|
|
Norbert,
Thanks for the heads up, but this is a known problem. The mailmain list is hosted by VMWare, but the web access is restricted to the internal internet. Use the mail-based api for all of your maintenance activities. This mailing list was "grandfathered in" so we are able to provide both the web-based and mail-based api ... Dale On Feb 5, 2011, at 4:01 AM, Norbert Hartl wrote: Dale, On 04.02.2011, at 20:14, Dale Henrichs wrote: I also encourage you to subscribe to the GemStoneBeta mailing list where discussions and further server beta related announcements will be made. To subscribe, send an e-mail with the single word "subscribe" (without quotes) in the subject line or body of the message to the list administrative address, [hidden email]<mailto:[hidden email]>. if you subscribe to the list you get mailman mail with a bogus link in the mail text. It has a subscription link that points to mailman2.vmware.com<http://mailman2.vmware.com/>. This hostname does not exist (not even in any vmware dns server). Probabily you can forward this to the person in charge. Norbert |
|
In reply to this post by Dale Henrichs
Hi Dale,
Is there a summary you can point me at of the new features we can look forward to in Gemstone 3.0? Nick
On 4 February 2011 19:14, Dale Henrichs <[hidden email]> wrote: Yesterday we announced the availability of GemStone 3.0.0Beta3. From the |
Re: GemStone/S 64 Bit 3.0.0Beta3 available
|
|
Many of the changes are covered in the 3.x release notes.
http://community.gemstone.com/download/attachments/6037520/GS64-ReleaseNotes-3.0Beta.pdf -- Monty From: "Nick Ager" <[hidden email]> To: "GemStone Seaside beta discussion" <[hidden email]> Sent: Saturday, February 5, 2011 11:21:33 AM Subject: Re: [GS/SS Beta] GemStone/S 64 Bit 3.0.0Beta3 available Hi Dale, Is there a summary you can point me at of the new features we can look forward to in Gemstone 3.0? Nick
On 4 February 2011 19:14, Dale Henrichs <[hidden email]> wrote: Yesterday we announced the availability of GemStone 3.0.0Beta3. From the |
|
|
On 6 February 2011 02:31, Monty Williams <[hidden email]> wrote:
Thanks, it looks like there's wealth of useful features and improvements in the 3.0 release. I guess the ones that struck me most for Seaside relevance would be:
* NotTranloggedGlobals - I understand can be used for Seaside sessions, resulting in significant performance improvements. * FFI * GsProcess multithreaded operations - I guess could allow one Gem to handle multiple simultaneous requests and/or fork a background task during a request.
* Ability to call Ruby code - I've just realised that this could be really useful as often web services have Ruby bindings, but no Smalltalk binding. ... as well as the numerous bug fixes and improved ANSI compliance.
Looking forward to the release immensely. |
Re: GemStone/S 64 Bit 3.0.0Beta3 available
|
|
In reply to this post by Dale Henrichs
Hi, is there a programming guide that covers 3.0 additions?
-Conrad
On Fri, Feb 4, 2011 at 11:14 AM, Dale Henrichs <[hidden email]> wrote: Yesterday we announced the availability of GemStone 3.0.0Beta3. From the |
Re: GemStone/S 64 Bit 3.0.0Beta3 available
|
|
In reply to this post by Nick
On 02/06/2011 05:44 AM, Nick Ager wrote:
> On 6 February 2011 02:31, Monty Williams <[hidden email] > <mailto:[hidden email]>> wrote: > > Many of the changes are covered in the 3.x release notes. > > http://community.gemstone.com/download/attachments/6037520/GS64-ReleaseNotes-3.0Beta.pdf > > > Thanks, it looks like there's wealth of useful features and > improvements in the 3.0 release. I guess the ones that struck me most > for Seaside relevance would be: > > * NotTranloggedGlobals - I understand can be used for Seaside sessions, > resulting in significant performance improvements. Yep, I plan to leverage this in the Seaside3.0 work that I'll be doing over the next several months. > * FFI > * GsProcess multithreaded operations - I guess could allow one Gem to > handle multiple simultaneous requests and/or fork a background task > during a request. I think you are referring to "New Multi-Threaded Operations" which are targetted at the specific operations mentioned in the docs: - object audit - mfc - list instances - etc. At this point in time there is no way for you to inject application logic into the multi-threaded framework ... Sorry:( > * Ability to call Ruby code - I've just realised that this could be > really useful as often web services have Ruby bindings, but no Smalltalk > binding. > > ... as well as the numerous bug fixes and improved ANSI compliance. |
Re: GemStone/S 64 Bit 3.0.0Beta3 available
|
|
In reply to this post by Conrad Taylor
Conrad,
Not yet....I assume that as the docs become available they'll be announced on the gemstone beta list and be available here: http://community.gemstone.com/display/GSS64/GemStoneS+64+Documentation Dale On 02/06/2011 11:22 AM, Conrad Taylor wrote: > Hi, is there a programming guide that covers 3.0 additions? > > -Conrad > > On Fri, Feb 4, 2011 at 11:14 AM, Dale Henrichs <[hidden email] > <mailto:[hidden email]>> wrote: > > Yesterday we announced the availability of GemStone 3.0.0Beta3. From the > announcement email: > > We have released GemStone/S 64 Bit 3.0.0Beta3. This is the third in a > series of beta releases previewing the next generation of the > GemStone/S Smalltalk object server. > > Archives of this release may be downloaded from the following URL: > > ftp://ftp.gemstone.com/pub/GemStone64/3.0.0Beta3/ > > Revised installation guides are available at the following URL: > > http://community.gemstone.com/display/GSS6 > /GemStoneS+64+bit+3.0+Beta+Documentation > > Seaside3.0 is functional on this release. There are a number of > tests that don't pass and the engineering team is continuing to fix > bugs in the server. > > If you want to kick the tires on 3.0 and Seaside3.0 then I encourage > you to take it for a spin. If you run into problems with GemTools or > Seaside or the base image code, please submit a glassdb issue and I > will route it to the engineering team if it is a base bug. > > I also encourage you to subscribe to the GemStoneBeta mailing list > where discussions and further server beta related announcements will > be made. To subscribe, send an e-mail with the single word > "subscribe" (without quotes) in the subject line or body of the > message to the list administrative address, > [hidden email] > <mailto:[hidden email]>. > > To work with GLASS and Seaside3.0 in GemStone3.0 you will need to > update to the latest GLASS 1.0-beta.8.6 and use version 3.0.3.1 of > Seaside. Both of these versions are under active development so it > is possible that there will be load/update issues over time. so it > is a good idea to backup before updating. > > Use the GemTools menu to update GLASS and use the following > expression to load/update Seaside3.0: > > Gofer new > squeaksource: 'Seaside30'; > package: 'ConfigurationOfSeaside30'; > package: 'ConfigurationOfGrease'; > load. > > GsDeployer deploy: [ > Gofer project load: 'Seaside30' version: '3.0.3.1' group: 'ALL'. > ] > > Note that I'm using GsDeployer class>deploy: instead of > MCPlatformSupport class>>commitOnAlmostOutOfMemoryDuring:. > GsDeployer class>deploy: does a commitOnAlmostOutOfMemoryDuring:, > handles Warnings by dumping the description to the transcript, turns > off autoMigrate, executes the block and then does a bulk migrate of > instances for all classes changed during update ... should result in > way faster upgrades and migrations... > > For the beta, there is no supported upgrade path between beta > releases, so don't do anything important in the beta. Also, for this > beta, there is no upgrade path from 2.4.4.1 to 3.0...that will be > forthcoming in a future release. > > Dale > > |
«
Return to GLASS
|
1 view|%1 views
| Free forum by Nabble | Edit this page |