GLASS upgrade path from GemStone 2.4.x to GemStone 3.1

Over the last week or so I have been working on providing an upgrade path from GLASS from 2.4.x to 3.1 ...

The 3.1 release is scheduled for a couple of months from now, but I thought I'd let you folks know ahead of time so you can plan accordingly.

The upgradeSeasideImage script will handle the basic migration of your repository from 2.4.x to 3.1 and the basic GLASS code will be loaded.

When the upgradeSeasideImage script completes you will need to load your own code into the repository and in order to do that, your code will have to be ported to GemStone3.x ...

For the pure port, you can use GemStone3.0.1 to ensure that your application code will run under 3.x. The most notable difference is that the Exception hierarchy in GemStone 3.x should be rooted in the Exception class instead of ExceptionA. There is also a much richer Exception eco-system that you might want to take advantage of in your 3.x version of your application.

There are other class library differences between GemStone 2.4.x and 3.x, but you may or may not run into those differences during your normal operations ...

So, if you've been waiting with bated breath for an upgrade path to GemStone 3.x, it's just around the corner and you can get a head start on things by porting your apps to 3.0.1. If you are planning a move to 3.1 when it's available, let me know which version of GemStone 2.4.x you are currently using, so that I can run against those specific versions. Finally, as we get closer to the release date, we can make candidate builds available for folks to do upgrade testing ... that way we can nail some of the infant mortality bugs that you might run into prior to the release when it will be much easier for us to insert the needed bug fixes ...

The current target date for the 3.1 release is June, so mark your calendars and let me know if you'd like access to candidate builds...


Dale

Dale,
  Put me on the list for candidate builds. Could you tell me some of the advantages of moving from 2.4.4.1 to 3.1?

  Larry Kellogg
  www.practicemusic.com


On Apr 23, 2012, at 2:21 PM, Dale Henrichs wrote:

Certainly, here's a link to Norm's STIC talk on "A review of new features in GemStone/64 version 3.0 and a look at what’s coming in version 3.1."[1].

Here are some highlights:

  - 25% to 100% speed improvement
  - Foreign Function Interface (FFI)
  - Multi-threaded Operations for MFC, backup and listInstances (native OS threads)
  - ByteArray Literal Syntax
  - New Tranlog AIO System
  - Significant Commit performance improvements
  - Hot Standby
  - Nested Transactions
  - Smalltalk level SSL Support

If you are interested in the SSL support, it would be a good idea to request early access so we can make sure that we can do what you need to do....

Dale

[1] http://www.stic.st/wp-content/conferences/2012/Tuesday/0915-GemStone64-Green.pdf

----- Original Message -----
| From: "Lawrence Kellogg" <[hidden email]>
| To: "GemStone Seaside beta discussion" <[hidden email]>
| Sent: Monday, April 23, 2012 1:39:19 PM
| Subject: Re: [GS/SS Beta] GLASS upgrade path from GemStone 2.4.x to GemStone 3.1
|
| Dale,
|   Put me on the list for candidate builds. Could you tell me some of
|   the advantages of moving from 2.4.4.1 to 3.1?
|
|   Larry Kellogg
|   www.practicemusic.com
|
|
| On Apr 23, 2012, at 2:21 PM, Dale Henrichs wrote:
|
| > Over the last week or so I have been working on providing an
| > upgrade path from GLASS from 2.4.x to 3.1 ...
| >
| > The 3.1 release is scheduled for a couple of months from now, but I
| > thought I'd let you folks know ahead of time so you can plan
| > accordingly.
| >
| > The upgradeSeasideImage script will handle the basic migration of
| > your repository from 2.4.x to 3.1 and the basic GLASS code will be
| > loaded.
| >
| > When the upgradeSeasideImage script completes you will need to load
| > your own code into the repository and in order to do that, your
| > code will have to be ported to GemStone3.x ...
| >
| > For the pure port, you can use GemStone3.0.1 to ensure that your
| > application code will run under 3.x. The most notable difference
| > is that the Exception hierarchy in GemStone 3.x should be rooted
| > in the Exception class instead of ExceptionA. There is also a much
| > richer Exception eco-system that you might want to take advantage
| > of in your 3.x version of your application.
| >
| > There are other class library differences between GemStone 2.4.x
| > and 3.x, but you may or may not run into those differences during
| > your normal operations ...
| >
| > So, if you've been waiting with bated breath for an upgrade path to
| > GemStone 3.x, it's just around the corner and you can get a head
| > start on things by porting your apps to 3.0.1. If you are planning
| > a move to 3.1 when it's available, let me know which version of
| > GemStone 2.4.x you are currently using, so that I can run against
| > those specific versions. Finally, as we get closer to the release
| > date, we can make candidate builds available for folks to do
| > upgrade testing ... that way we can nail some of the infant
| > mortality bugs that you might run into prior to the release when
| > it will be much easier for us to insert the needed bug fixes ...
| >
| > The current target date for the 3.1 release is June, so mark your
| > calendars and let me know if you'd like access to candidate
| > builds...
| >
| >
| > Dale
|
|

On Apr 23, 2012, at 11:21 AM, Dale Henrichs wrote:

Dale, can you add me to the list for release candidate builds for Gemstone/S 3.1?

Think different and code well,

-Conrad

> The current target date for the 3.1 release is June, so mark your calendars and let me know if you'd like access to candidate builds...
>
>
> Dale

Dale,

SSL support makes me really want to upgrade soon. Please add me! Great stuff :)

Norbert


Am 23.04.2012 um 23:09 schrieb Dale Henrichs:

Hi Dale,

Thanks, this is great.

Something we did on the previous upgrade was to essentially nuke all
the GLASS code out of GS, upgrade (normal GS image upgrade) bootstrap
and load GLASS again. Will this kind of approach work again?

Cheers
Otto

On Mon, Apr 23, 2012 at 8:21 PM, Dale Henrichs <[hidden email]> wrote:

Otto,

Yes that's pretty much the current upgrade scheme. In 3.x it is required that all of the methods be recompiled so part of the process is to strip all of the methods from the non-base classes ... for a standard install that would be all of the classes in UserGlobals get their methods nuked ... the upgrade script automatically loads the GLASS code, then you will have to load all of your application code.

Some of the classes like ExceptionA have been obsoleted so it is also necessary to redefine all of the classes, so that they are subclassed off of the right superclass. It's one of the reasons I am recommending that you get a head start on porting your applications to 3.0 ... so that you don't have to deal with porting issues while upgrading your repository...

Dale

----- Original Message -----
| From: "Otto Behrens" <[hidden email]>
| To: "GemStone Seaside beta discussion" <[hidden email]>
| Sent: Tuesday, April 24, 2012 9:05:57 AM
| Subject: Re: [GS/SS Beta] GLASS upgrade path from GemStone 2.4.x to GemStone 3.1
|
| Hi Dale,
|
| Thanks, this is great.
|
| Something we did on the previous upgrade was to essentially nuke all
| the GLASS code out of GS, upgrade (normal GS image upgrade) bootstrap
| and load GLASS again. Will this kind of approach work again?
|
| Cheers
| Otto
|
| On Mon, Apr 23, 2012 at 8:21 PM, Dale Henrichs <[hidden email]>
| wrote:
| > Over the last week or so I have been working on providing an
| > upgrade path from GLASS from 2.4.x to 3.1 ...
| >
| > The 3.1 release is scheduled for a couple of months from now, but I
| > thought I'd let you folks know ahead of time so you can plan
| > accordingly.
| >
| > The upgradeSeasideImage script will handle the basic migration of
| > your repository from 2.4.x to 3.1 and the basic GLASS code will be
| > loaded.
| >
| > When the upgradeSeasideImage script completes you will need to load
| > your own code into the repository and in order to do that, your
| > code will have to be ported to GemStone3.x ...
| >
| > For the pure port, you can use GemStone3.0.1 to ensure that your
| > application code will run under 3.x. The most notable difference
| > is that the Exception hierarchy in GemStone 3.x should be rooted
| > in the Exception class instead of ExceptionA. There is also a much
| > richer Exception eco-system that you might want to take advantage
| > of in your 3.x version of your application.
| >
| > There are other class library differences between GemStone 2.4.x
| > and 3.x, but you may or may not run into those differences during
| > your normal operations ...
| >
| > So, if you've been waiting with bated breath for an upgrade path to
| > GemStone 3.x, it's just around the corner and you can get a head
| > start on things by porting your apps to 3.0.1. If you are planning
| > a move to 3.1 when it's available, let me know which version of
| > GemStone 2.4.x you are currently using, so that I can run against
| > those specific versions. Finally, as we get closer to the release
| > date, we can make candidate builds available for folks to do
| > upgrade testing ... that way we can nail some of the infant
| > mortality bugs that you might run into prior to the release when
| > it will be much easier for us to insert the needed bug fixes ...
| >
| > The current target date for the 3.1 release is June, so mark your
| > calendars and let me know if you'd like access to candidate
| > builds...
| >
| >
| > Dale
|

Thanks for the feedback ...

When we start creating candidate builds (it'll be at least a couple of weeks), I'll announce here.

If you are working on porting your app to GemStone3.0 for an eventual upgrade to 3.1 from 2.4, then I suggest that you use GLASS 1.0-beta.8.7.2 as the basis ...

1.0-beta.8.7.2 is in development and I periodically make updates as I find issues that need addressing ... I plan to release 1.0-beta.8.7.2 when I've finished my 3.1 work.

If you hit issues, just let me know...

Dale

----- Original Message -----
| From: "Dale Henrichs" <[hidden email]>
| To: "GemStone Seaside beta discussion" <[hidden email]>
| Sent: Tuesday, April 24, 2012 9:24:12 AM
| Subject: Re: [GS/SS Beta] GLASS upgrade path from GemStone 2.4.x to GemStone 3.1
|
| Otto,
|
| Yes that's pretty much the current upgrade scheme. In 3.x it is
| required that all of the methods be recompiled so part of the
| process is to strip all of the methods from the non-base classes ...
| for a standard install that would be all of the classes in
| UserGlobals get their methods nuked ... the upgrade script
| automatically loads the GLASS code, then you will have to load all
| of your application code.
|
| Some of the classes like ExceptionA have been obsoleted so it is also
| necessary to redefine all of the classes, so that they are
| subclassed off of the right superclass. It's one of the reasons I am
| recommending that you get a head start on porting your applications
| to 3.0 ... so that you don't have to deal with porting issues while
| upgrading your repository...
|
| Dale
|
| ----- Original Message -----
| | From: "Otto Behrens" <[hidden email]>
| | To: "GemStone Seaside beta discussion" <[hidden email]>
| | Sent: Tuesday, April 24, 2012 9:05:57 AM
| | Subject: Re: [GS/SS Beta] GLASS upgrade path from GemStone 2.4.x to
| | GemStone 3.1
| |
| | Hi Dale,
| |
| | Thanks, this is great.
| |
| | Something we did on the previous upgrade was to essentially nuke
| | all
| | the GLASS code out of GS, upgrade (normal GS image upgrade)
| | bootstrap
| | and load GLASS again. Will this kind of approach work again?
| |
| | Cheers
| | Otto
| |
| | On Mon, Apr 23, 2012 at 8:21 PM, Dale Henrichs
| | <[hidden email]>
| | wrote:
| | > Over the last week or so I have been working on providing an
| | > upgrade path from GLASS from 2.4.x to 3.1 ...
| | >
| | > The 3.1 release is scheduled for a couple of months from now, but
| | > I
| | > thought I'd let you folks know ahead of time so you can plan
| | > accordingly.
| | >
| | > The upgradeSeasideImage script will handle the basic migration of
| | > your repository from 2.4.x to 3.1 and the basic GLASS code will
| | > be
| | > loaded.
| | >
| | > When the upgradeSeasideImage script completes you will need to
| | > load
| | > your own code into the repository and in order to do that, your
| | > code will have to be ported to GemStone3.x ...
| | >
| | > For the pure port, you can use GemStone3.0.1 to ensure that your
| | > application code will run under 3.x. The most notable difference
| | > is that the Exception hierarchy in GemStone 3.x should be rooted
| | > in the Exception class instead of ExceptionA. There is also a
| | > much
| | > richer Exception eco-system that you might want to take advantage
| | > of in your 3.x version of your application.
| | >
| | > There are other class library differences between GemStone 2.4.x
| | > and 3.x, but you may or may not run into those differences during
| | > your normal operations ...
| | >
| | > So, if you've been waiting with bated breath for an upgrade path
| | > to
| | > GemStone 3.x, it's just around the corner and you can get a head
| | > start on things by porting your apps to 3.0.1. If you are
| | > planning
| | > a move to 3.1 when it's available, let me know which version of
| | > GemStone 2.4.x you are currently using, so that I can run against
| | > those specific versions. Finally, as we get closer to the release
| | > date, we can make candidate builds available for folks to do
| | > upgrade testing ... that way we can nail some of the infant
| | > mortality bugs that you might run into prior to the release when
| | > it will be much easier for us to insert the needed bug fixes ...
| | >
| | > The current target date for the 3.1 release is June, so mark your
| | > calendars and let me know if you'd like access to candidate
| | > builds...
| | >
| | >
| | > Dale
| |
|

Norbert, et.al,,

Regarding the Smalltalk SSL support ... if you have the time to take the new SSL support for a spin, I would imagine that we'd give you early access to one of our engineering builds for the express purpose of getting feedback on our SSL support ... then we'd be able to get a jump on any bugs that your find or even better find any important bits that we've left out ...

If there are volunteers, I'll check with management and see what we can arrange ...

Dale

----- Original Message -----
| From: "Norbert Hartl" <[hidden email]>
| To: "GemStone Seaside beta discussion" <[hidden email]>
| Sent: Tuesday, April 24, 2012 12:16:27 AM
| Subject: Re: [GS/SS Beta] GLASS upgrade path from GemStone 2.4.x to GemStone 3.1
|
| Dale,
|
| SSL support makes me really want to upgrade soon. Please add me!
| Great stuff :)
|
| Norbert
|
|
| Am 23.04.2012 um 23:09 schrieb Dale Henrichs:
|
| > Certainly, here's a link to Norm's STIC talk on "A review of new
| > features in GemStone/64 version 3.0 and a look at what’s coming in
| > version 3.1."[1].
| >
| > Here are some highlights:
| >
| >  - 25% to 100% speed improvement
| >  - Foreign Function Interface (FFI)
| >  - Multi-threaded Operations for MFC, backup and listInstances
| >  (native OS threads)
| >  - ByteArray Literal Syntax
| >  - New Tranlog AIO System
| >  - Significant Commit performance improvements
| >  - Hot Standby
| >  - Nested Transactions
| >  - Smalltalk level SSL Support
| >
| > If you are interested in the SSL support, it would be a good idea
| > to request early access so we can make sure that we can do what
| > you need to do....
| >
| > Dale
| >
| > [1]
| > http://www.stic.st/wp-content/conferences/2012/Tuesday/0915-GemStone64-Green.pdf
| >
| > ----- Original Message -----
| > | From: "Lawrence Kellogg" <[hidden email]>
| > | To: "GemStone Seaside beta discussion"
| > | <[hidden email]>
| > | Sent: Monday, April 23, 2012 1:39:19 PM
| > | Subject: Re: [GS/SS Beta] GLASS upgrade path from GemStone 2.4.x
| > | to GemStone 3.1
| > |
| > | Dale,
| > |   Put me on the list for candidate builds. Could you tell me some
| > |   of
| > |   the advantages of moving from 2.4.4.1 to 3.1?
| > |
| > |   Larry Kellogg
| > |   www.practicemusic.com
| > |
| > |
| > | On Apr 23, 2012, at 2:21 PM, Dale Henrichs wrote:
| > |
| > | > Over the last week or so I have been working on providing an
| > | > upgrade path from GLASS from 2.4.x to 3.1 ...
| > | >
| > | > The 3.1 release is scheduled for a couple of months from now,
| > | > but I
| > | > thought I'd let you folks know ahead of time so you can plan
| > | > accordingly.
| > | >
| > | > The upgradeSeasideImage script will handle the basic migration
| > | > of
| > | > your repository from 2.4.x to 3.1 and the basic GLASS code will
| > | > be
| > | > loaded.
| > | >
| > | > When the upgradeSeasideImage script completes you will need to
| > | > load
| > | > your own code into the repository and in order to do that, your
| > | > code will have to be ported to GemStone3.x ...
| > | >
| > | > For the pure port, you can use GemStone3.0.1 to ensure that
| > | > your
| > | > application code will run under 3.x. The most notable
| > | > difference
| > | > is that the Exception hierarchy in GemStone 3.x should be
| > | > rooted
| > | > in the Exception class instead of ExceptionA. There is also a
| > | > much
| > | > richer Exception eco-system that you might want to take
| > | > advantage
| > | > of in your 3.x version of your application.
| > | >
| > | > There are other class library differences between GemStone
| > | > 2.4.x
| > | > and 3.x, but you may or may not run into those differences
| > | > during
| > | > your normal operations ...
| > | >
| > | > So, if you've been waiting with bated breath for an upgrade
| > | > path to
| > | > GemStone 3.x, it's just around the corner and you can get a
| > | > head
| > | > start on things by porting your apps to 3.0.1. If you are
| > | > planning
| > | > a move to 3.1 when it's available, let me know which version of
| > | > GemStone 2.4.x you are currently using, so that I can run
| > | > against
| > | > those specific versions. Finally, as we get closer to the
| > | > release
| > | > date, we can make candidate builds available for folks to do
| > | > upgrade testing ... that way we can nail some of the infant
| > | > mortality bugs that you might run into prior to the release
| > | > when
| > | > it will be much easier for us to insert the needed bug fixes
| > | > ...
| > | >
| > | > The current target date for the 3.1 release is June, so mark
| > | > your
| > | > calendars and let me know if you'd like access to candidate
| > | > builds...
| > | >
| > | >
| > | > Dale
| > |
| > |
|
|

Dale,

Am 25.04.2012 um 18:33 schrieb Dale Henrichs:

> Norbert, et.al,,
>
> Regarding the Smalltalk SSL support ... if you have the time to take the new SSL support for a spin, I would imagine that we'd give you early access to one of our engineering builds for the express purpose of getting feedback on our SSL support ... then we'd be able to get a jump on any bugs that your find or even better find any important bits that we've left out ...
>
I could try it out. I think I could do it somewhere next week. Can you give some information what is the scope of the support upfront? Is it plain SSL support meaning you added libssl per FFI? Or is the support incorporated somewhere: http client, http server, smtp client? Will there be support for server certificates _and_ client certificates?
To test it I would need the Mac OS version running because I have Linux only in the cloud (dunno where :) ) and that is bad for testing thoroughly.

> If there are volunteers, I'll check with management and see what we can arrange ...
>
Norbert

Norbert,

I've shipped you the current source via separate email and I'll be shipping you the draft of the socket chapter which includes a section on ssl ...

Mac version is no problem ... we build and test the mac version all the time ...

Dale

----- Original Message -----
| From: "Norbert Hartl" <[hidden email]>
| To: "GemStone Seaside beta discussion" <[hidden email]>
| Sent: Thursday, April 26, 2012 1:13:25 AM
| Subject: Re: [GS/SS Beta] GLASS upgrade path from GemStone 2.4.x to GemStone 3.1
|
| Dale,
|
| Am 25.04.2012 um 18:33 schrieb Dale Henrichs:
|
| > Norbert, et.al,,
| >
| > Regarding the Smalltalk SSL support ... if you have the time to
| > take the new SSL support for a spin, I would imagine that we'd
| > give you early access to one of our engineering builds for the
| > express purpose of getting feedback on our SSL support ... then
| > we'd be able to get a jump on any bugs that your find or even
| > better find any important bits that we've left out ...
| >
| I could try it out. I think I could do it somewhere next week. Can
| you give some information what is the scope of the support upfront?
| Is it plain SSL support meaning you added libssl per FFI? Or is the
| support incorporated somewhere: http client, http server, smtp
| client? Will there be support for server certificates _and_ client
| certificates?
| To test it I would need the Mac OS version running because I have
| Linux only in the cloud (dunno where :) ) and that is bad for
| testing thoroughly.
|
| > If there are volunteers, I'll check with management and see what we
| > can arrange ...
| >
| Norbert
|
| > ----- Original Message -----
| > | From: "Norbert Hartl" <[hidden email]>
| > | To: "GemStone Seaside beta discussion"
| > | <[hidden email]>
| > | Sent: Tuesday, April 24, 2012 12:16:27 AM
| > | Subject: Re: [GS/SS Beta] GLASS upgrade path from GemStone 2.4.x
| > | to GemStone 3.1
| > |
| > | Dale,
| > |
| > | SSL support makes me really want to upgrade soon. Please add me!
| > | Great stuff :)
| > |
| > | Norbert
| > |
| > |
| > | Am 23.04.2012 um 23:09 schrieb Dale Henrichs:
| > |
| > | > Certainly, here's a link to Norm's STIC talk on "A review of
| > | > new
| > | > features in GemStone/64 version 3.0 and a look at what’s coming
| > | > in
| > | > version 3.1."[1].
| > | >
| > | > Here are some highlights:
| > | >
| > | >  - 25% to 100% speed improvement
| > | >  - Foreign Function Interface (FFI)
| > | >  - Multi-threaded Operations for MFC, backup and listInstances
| > | >  (native OS threads)
| > | >  - ByteArray Literal Syntax
| > | >  - New Tranlog AIO System
| > | >  - Significant Commit performance improvements
| > | >  - Hot Standby
| > | >  - Nested Transactions
| > | >  - Smalltalk level SSL Support
| > | >
| > | > If you are interested in the SSL support, it would be a good
| > | > idea
| > | > to request early access so we can make sure that we can do what
| > | > you need to do....
| > | >
| > | > Dale
| > | >
| > | > [1]
| > | > http://www.stic.st/wp-content/conferences/2012/Tuesday/0915-GemStone64-Green.pdf
| > | >
| > | > ----- Original Message -----
| > | > | From: "Lawrence Kellogg" <[hidden email]>
| > | > | To: "GemStone Seaside beta discussion"
| > | > | <[hidden email]>
| > | > | Sent: Monday, April 23, 2012 1:39:19 PM
| > | > | Subject: Re: [GS/SS Beta] GLASS upgrade path from GemStone
| > | > | 2.4.x
| > | > | to GemStone 3.1
| > | > |
| > | > | Dale,
| > | > |   Put me on the list for candidate builds. Could you tell me
| > | > |   some
| > | > |   of
| > | > |   the advantages of moving from 2.4.4.1 to 3.1?
| > | > |
| > | > |   Larry Kellogg
| > | > |   www.practicemusic.com
| > | > |
| > | > |
| > | > | On Apr 23, 2012, at 2:21 PM, Dale Henrichs wrote:
| > | > |
| > | > | > Over the last week or so I have been working on providing
| > | > | > an
| > | > | > upgrade path from GLASS from 2.4.x to 3.1 ...
| > | > | >
| > | > | > The 3.1 release is scheduled for a couple of months from
| > | > | > now,
| > | > | > but I
| > | > | > thought I'd let you folks know ahead of time so you can
| > | > | > plan
| > | > | > accordingly.
| > | > | >
| > | > | > The upgradeSeasideImage script will handle the basic
| > | > | > migration
| > | > | > of
| > | > | > your repository from 2.4.x to 3.1 and the basic GLASS code
| > | > | > will
| > | > | > be
| > | > | > loaded.
| > | > | >
| > | > | > When the upgradeSeasideImage script completes you will need
| > | > | > to
| > | > | > load
| > | > | > your own code into the repository and in order to do that,
| > | > | > your
| > | > | > code will have to be ported to GemStone3.x ...
| > | > | >
| > | > | > For the pure port, you can use GemStone3.0.1 to ensure that
| > | > | > your
| > | > | > application code will run under 3.x. The most notable
| > | > | > difference
| > | > | > is that the Exception hierarchy in GemStone 3.x should be
| > | > | > rooted
| > | > | > in the Exception class instead of ExceptionA. There is also
| > | > | > a
| > | > | > much
| > | > | > richer Exception eco-system that you might want to take
| > | > | > advantage
| > | > | > of in your 3.x version of your application.
| > | > | >
| > | > | > There are other class library differences between GemStone
| > | > | > 2.4.x
| > | > | > and 3.x, but you may or may not run into those differences
| > | > | > during
| > | > | > your normal operations ...
| > | > | >
| > | > | > So, if you've been waiting with bated breath for an upgrade
| > | > | > path to
| > | > | > GemStone 3.x, it's just around the corner and you can get a
| > | > | > head
| > | > | > start on things by porting your apps to 3.0.1. If you are
| > | > | > planning
| > | > | > a move to 3.1 when it's available, let me know which
| > | > | > version of
| > | > | > GemStone 2.4.x you are currently using, so that I can run
| > | > | > against
| > | > | > those specific versions. Finally, as we get closer to the
| > | > | > release
| > | > | > date, we can make candidate builds available for folks to
| > | > | > do
| > | > | > upgrade testing ... that way we can nail some of the infant
| > | > | > mortality bugs that you might run into prior to the release
| > | > | > when
| > | > | > it will be much easier for us to insert the needed bug
| > | > | > fixes
| > | > | > ...
| > | > | >
| > | > | > The current target date for the 3.1 release is June, so
| > | > | > mark
| > | > | > your
| > | > | > calendars and let me know if you'd like access to candidate
| > | > | > builds...
| > | > | >
| > | > | >
| > | > | > Dale
| > | > |
| > | > |
| > |
| > |
|
|

When I composed this list I forgot to mention that we are greatly improving our Unicode support. We are providing a Smalltalk API for ICU[1], which means that we should have complete support for Unicode.

Dale

[1] http://site.icu-project.org/

----- Original Message -----
| From: "Dale Henrichs" <[hidden email]>
| To: "GemStone Seaside beta discussion" <[hidden email]>
| Sent: Monday, April 23, 2012 2:09:15 PM
| Subject: Re: [GS/SS Beta] GLASS upgrade path from GemStone 2.4.x to GemStone 3.1
|
| Certainly, here's a link to Norm's STIC talk on "A review of new
| features in GemStone/64 version 3.0 and a look at what’s coming in
| version 3.1."[1].
|
| Here are some highlights:
|
|   - 25% to 100% speed improvement
|   - Foreign Function Interface (FFI)
|   - Multi-threaded Operations for MFC, backup and listInstances
|   (native OS threads)
|   - ByteArray Literal Syntax
|   - New Tranlog AIO System
|   - Significant Commit performance improvements
|   - Hot Standby
|   - Nested Transactions
|   - Smalltalk level SSL Support
|
| If you are interested in the SSL support, it would be a good idea to
| request early access so we can make sure that we can do what you
| need to do....
|
| Dale
|
| [1]
| http://www.stic.st/wp-content/conferences/2012/Tuesday/0915-GemStone64-Green.pdf
|
| ----- Original Message -----
| | From: "Lawrence Kellogg" <[hidden email]>
| | To: "GemStone Seaside beta discussion" <[hidden email]>
| | Sent: Monday, April 23, 2012 1:39:19 PM
| | Subject: Re: [GS/SS Beta] GLASS upgrade path from GemStone 2.4.x to
| | GemStone 3.1
| |
| | Dale,
| |   Put me on the list for candidate builds. Could you tell me some
| |   of
| |   the advantages of moving from 2.4.4.1 to 3.1?
| |
| |   Larry Kellogg
| |   www.practicemusic.com
| |
| |
| | On Apr 23, 2012, at 2:21 PM, Dale Henrichs wrote:
| |
| | > Over the last week or so I have been working on providing an
| | > upgrade path from GLASS from 2.4.x to 3.1 ...
| | >
| | > The 3.1 release is scheduled for a couple of months from now, but
| | > I
| | > thought I'd let you folks know ahead of time so you can plan
| | > accordingly.
| | >
| | > The upgradeSeasideImage script will handle the basic migration of
| | > your repository from 2.4.x to 3.1 and the basic GLASS code will
| | > be
| | > loaded.
| | >
| | > When the upgradeSeasideImage script completes you will need to
| | > load
| | > your own code into the repository and in order to do that, your
| | > code will have to be ported to GemStone3.x ...
| | >
| | > For the pure port, you can use GemStone3.0.1 to ensure that your
| | > application code will run under 3.x. The most notable difference
| | > is that the Exception hierarchy in GemStone 3.x should be rooted
| | > in the Exception class instead of ExceptionA. There is also a
| | > much
| | > richer Exception eco-system that you might want to take advantage
| | > of in your 3.x version of your application.
| | >
| | > There are other class library differences between GemStone 2.4.x
| | > and 3.x, but you may or may not run into those differences during
| | > your normal operations ...
| | >
| | > So, if you've been waiting with bated breath for an upgrade path
| | > to
| | > GemStone 3.x, it's just around the corner and you can get a head
| | > start on things by porting your apps to 3.0.1. If you are
| | > planning
| | > a move to 3.1 when it's available, let me know which version of
| | > GemStone 2.4.x you are currently using, so that I can run against
| | > those specific versions. Finally, as we get closer to the release
| | > date, we can make candidate builds available for folks to do
| | > upgrade testing ... that way we can nail some of the infant
| | > mortality bugs that you might run into prior to the release when
| | > it will be much easier for us to insert the needed bug fixes ...
| | >
| | > The current target date for the 3.1 release is June, so mark your
| | > calendars and let me know if you'd like access to candidate
| | > builds...
| | >
| | >
| | > Dale
| |
| |
|

Hello,
  So, I want to use JSON to return objects from Gemstone. I'm new to JSON so bear with me.
If I define,

json
        ^ JSJson context: self renderContext

and

renderContext
        "Answer a fake rendering context for this pusher."

        ^ WARenderContext new
                document: (WAHtmlDocument on: (WriteStream on: String new));
                actionUrl: WAUrl new;
                yourself

in a subclass of WAComponent

and then do

(self json stringify: 'Login Succeeded') greaseString

I get this:

'JSON.stringify("Login Succeeded")'

Is this really what a JSON client would be able to decode? Seems wrong to me.
Which JSON package should I use in Gemstone? I'm using the Javascript-Core-JSON package.

  Any help would be appreciated.

  Regards,

  Larry

P.S. By the way, the client will not be written in Smalltalk, so I assume STON is not what I want, but I don't really know.

Larry,

I'm not quite prepared to say exactly how to return JSON from Seaside but it should just be a String. I can say a little bit about generating JSON in GemStone. We have a little bit of support for creating (but not parsing) JSON in 3.0. You can see the methods if you look at implementers of #'printJsonOn:'. Basically, you can send #'asJson' to certain objects and get a String. If you are in 2.x and want to use the code, you can download 3.0.1 and then in a shell in the product directory a grep for 'printJsonOn:' will show the following files:

$ grep -l printJsonOn: upgrade/*
upgrade/abstractdictionary.gs
upgrade/boolean.gs
upgrade/charcoll.gs
upgrade/collect.gs
upgrade/integer2.gs
upgrade/number.gs
upgrade/object.gs
upgrade/sequenc.gs
upgrade/sourcestrings.obj
upgrade/undefin.gs

You could add the appropriate methods (as SystemUser) in a 2.x repository and get the same behavior. The primary area of concern is to stay away from circular references since that would cause an out-of-memory condition (or out-of-stack, whichever came first!).

James

On May 6, 2012, at 11:00 AM, Lawrence Kellogg wrote:

On May 6, 2012, at 2:14 PM, James Foster wrote:

James,
  Thanks! I will look into pulling those methods into my staging 2.4.4.1 image and work on generating JSON. At this time, generating JSON will be sufficient.
I can worry about parsing JSON at some point in the future.

  Yes, I have run into quite a few out of memory, stack overflow conditions just trying to use the JSON methods in my image.

  Regards,

  Larry

On Sun, May 6, 2012 at 8:00 PM, Lawrence Kellogg <[hidden email]> wrote:
Can you provide a bit more information about the application you're
going to write? Does the server just return JSON or will it return
mostly HTML and JSON just in one place?

Which programming model are you looking for?
 - Do you want the traditional Seaside component model where a
response is made up of rendering all the visible components. Where you
have WATakss and components can #call: and #answer: and you have
"ugly" URLs.
 - Is the application more a web service style where it's important to
have nice and clean URLs and you don't have complex interaction.

Cheers
Philippe

Sent from my iPhone

On May 6, 2012, at 4:09 PM, Philippe Marschall <[hidden email]> wrote:

On Sun, May 6, 2012 at 8:00 PM, Lawrence Kellogg <[hidden email]> wrote:

Hello,

So, I want to use JSON to return objects from Gemstone. I'm new to JSON so bear with me.

If I define,

json

      ^ JSJson context: self renderContext

and

renderContext

      "Answer a fake rendering context for this pusher."

      ^ WARenderContext new

              document: (WAHtmlDocument on: (WriteStream on: String new));

              actionUrl: WAUrl new;

              yourself

in a subclass of WAComponent

and then do

(self json stringify: 'Login Succeeded') greaseString

I get this:

'JSON.stringify("Login Succeeded")'

Is this really what a JSON client would be able to decode? Seems wrong to me.

Which JSON package should I use in Gemstone? I'm using the Javascript-Core-JSON package.

Any help would be appreciated.

Can you provide a bit more information about the application you're

going to write? Does the server just return JSON or will it return

mostly HTML and JSON just in one place?

Hello,
  I have run into a weird rendering issue on the iPad. One of my imageButtons is  truncated so that part of it is not visible. The button works fine.

  This only happens to one of my imageButtons so I don't know what is going on.

  Any ideas?

 Larry

Larry,

YOu might also want to post on the seaside list... oh and I don't have an answer:)

Dale

----- Original Message -----
| From: "Lawrence Kellogg" <[hidden email]>
| To: "GemStone Seaside beta discussion" <[hidden email]>
| Sent: Sunday, May 6, 2012 1:46:47 PM
| Subject: [GS/SS Beta] imageButton truncated on iPad
|
| Hello,
|   I have run into a weird rendering issue on the iPad. One of my
|   imageButtons is  truncated so that part of it is not visible. The
|   button works fine.
|
|   This only happens to one of my imageButtons so I don't know what is
|   going on.
|
|   Any ideas?
|
|  Larry
|

Larry,

`'JSON.stringify("Login Succeeded")'` looks like the javascript code that will generate the JSON when executed in the browser.

There's a Seaside-JSON-Core package available that allows you to build a JSON-based response to a RESTful seaside request (so you can return JSON instead of HTML) in a Seaside style, i.e., #renderJsonOn:...

If you're using Seaside in your app then leveraging the explicit JSON support is a good way to go...

Dale

----- Original Message -----
| From: "Lawrence Kellogg" <[hidden email]>
| To: "GemStone Seaside beta discussion" <[hidden email]>
| Sent: Sunday, May 6, 2012 11:00:53 AM
| Subject: [GS/SS Beta] JSON Question
|
| Hello,
|   So, I want to use JSON to return objects from Gemstone. I'm new to
|   JSON so bear with me.
| If I define,
|
| json
| ^ JSJson context: self renderContext
|
| and
|
| renderContext
| "Answer a fake rendering context for this pusher."
|
| ^ WARenderContext new
| document: (WAHtmlDocument on: (WriteStream on: String new));
| actionUrl: WAUrl new;
| yourself
|
| in a subclass of WAComponent
|
| and then do
|
| (self json stringify: 'Login Succeeded') greaseString
|
| I get this:
|
| 'JSON.stringify("Login Succeeded")'
|
| Is this really what a JSON client would be able to decode? Seems
| wrong to me.
| Which JSON package should I use in Gemstone? I'm using the
| Javascript-Core-JSON package.
|
|   Any help would be appreciated.
|
|   Regards,
|
|   Larry
|
| P.S. By the way, the client will not be written in Smalltalk, so I
| assume STON is not what I want, but I don't really know.
|