PUM3 – Current State

DateAndTime exchange format is now RFC3339 (or at least some substandard). I was surprised to see, that even this format is not always supported in different langauges (without loading third party libraries) … but we got a minimum standard for Gemstone/S, ExtJS (Sencha) and Python. That should be enough.

Removing cookies support broke too much, therefore we have to support the old obsolete cookie support stuff and the new parameter based approach.

We started a new project with different needs. Therefore we had to improve the definition and handling of indices in Gemstone – actually we have to get experiences with indices first. We had no need to use them in previous projects.

We added support for IdentitySet as the base class for indexed associations on Gemstone side. The performance difference between Set and IdentitySet is remarkable.

Now we are adding support for new data types (we used in a new project): Duration (Server and Client), Point (Server), Rectangle (Server) and Colors (Server). That means, that these datatypes are available in the modelling tool.

The next wish is to have support for functions in attributes (in server domain classes – defined in the modelling tool by entering Smalltalk code)) – to have calculated attributes.

This entry was posted in Smalltalk and tagged , , , , . Bookmark the permalink.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s