Magma July 2008

magma@lists.squeakfoundation.org

5 participants
4 discussions

r41Beta7
by Chris Muller 28 Jul '08

28 Jul '08

I have just posted a new configuration, "r41Beta7" to the "MagmaTester" project of squeaksource. - Automatically turn off the new compression feature if the user is connecting to a locally-hosted server. In that scenario, compression slows things down. Note compressionThreshold will remain at the default for server responses, it must be explicitly changed. - Several fixes and improvements to ForwardingProxy's: - They can now be created for non-persistent objects in the image, allowing multi-repository models run with or without a repository seamlessly. - #realObject is now available on Object for seamless api with MagmaForwardingProxy. - Added MaSaveAndExitImageRequest, facilitating remote-shutdown of a headless server. - The compressThreshold api is now available on the server side. - Any object in the image can now answer the Magma #session it belongs to. - Improved error-handling for several situations. - The SUnit test script now instructs the client-player images to unload the server package during image startup, proving they can complete the suite without the server package loaded. - Renamed #mutatingProxyOid to #maOid. - Now printing the location in a MagmaSession printString! - Introducing MagmaSession>>#hasDefinition. This has actually been around for a while, but it's importance has not ever been properly noted. It answers whether this MagmaSession instance has ever been connected to a repository. Once connected to a particular repository, a MagmaSession may only reconnect to that same repository, not to any other repository. A new MagmaSession instance must be used to connect to a different repository.

3 3

r41Beta6
by Chris Muller 09 Jul '08

09 Jul '08

More improvements. - Added two new special operators specifically for MaKeywordIndexes; #includesAllPrefixes: and includesAnyPrefix:. These allow keyword searching by keyword *prefixes*, so the ending of the words doesn't have to be correctly guessed. - Clients and server may now specify their own #compressThreshold:, which affects the messages they send. Requests larger than this threshold will be compressed. #useCompression: is also included to avoid compression altogether. This would be desirable for web applications where multiple web clients are connected to a separage Magma server image running on the same machine. Since there is no network transport, compression is wasteful. - Removed "hostAddress" nomenclature in all public API's. Ip addresses may still be specified by using a hostname of '1.2.3.4'. This version is recommended for on-going development.

2 1

How to install latest Magma beta, let's try this again..
by Chris Muller 06 Jul '08

06 Jul '08

Ok, there continue to be questions about "how do I install Magma?" Unfortunately 3.9 was delivered with Monticello Configurations totally broken and even Monticello 1.5 does not seem fix it. I have not tried LevelPlayingField yet, but if you want a smaller simpler fix, I have attached two (previously-published) packages to this e-mail that you can load into a standard 3.9-7067 image so you can actually use Monticello Configurations. Here are the steps to load the latest and greatest Magma. 1) boot up a standard 3.9-7067 image. 2) load the attached Monticello-SR.315.mcz. 3) load the attached MonticelloConfigurations-cmm.44.mcz. 4) add the following HTTP repository to Monticello's repository list: MCHttpRepository location: 'http://www.squeaksource.com/MagmaTester' user: '' password: '' 5) Scroll down to the bottom of the package list, you should see "r41Beta4". 6) Click it, in the right-hand pane you see "r41Beta4.mcm". This is a MonticelloConfiguration file, it simply lists all of the packages for that configuration. Click it. 7) Click "Load". Magma is now loaded. Please let me know if further clarification is still needed. I'm sorry it is not easier. 3.9, in itself, was the most painful release of Squeak ever IMO. I have more than a dozen patches to the 7067 image just to get to an image with basic tool stability, doesn't everyone? My personal goal is for you to have a "one-click" load and then a reasonably stable and working ODBMS. Is Magma the only system out there made up of multiple independent Monticello packages? Someone please tell me what is the best practice for deployment of such a system and I will be happy to do it. - Chris PS - Note, this mail is about loading the *beta* release of Magma. At this time, barring any super solutions to Squeaks packaging systems, I plan for the *Stable* release of Magma will continue to be SAR. SAR's offer unlimited flexibility and compatible across all recent versions of Squeak (since 3.7 I think).

2 1

multiple concurrent access?
by sol tourne 01 Jul '08

01 Jul '08

hi - I have a server with 6 different seaside images (with different applications) all connecting to the same user database. Can magma handle such a scenario with several concurrent access (vast majority is read, but all can write) from various seaside applications in distinct images? (The information I found on the wiki seemed somewhat contradictory in this respect, so I'm double-checking here, sorry for the noise!) ts

2 1

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

Magma July 2008