Magma

magma@lists.squeakfoundation.org

722 discussions

[ANN] Magma and Seaside Integration Support
by Brent Pinkney 05 Dec '05

05 Dec '05

Hi, The Magma team is proud to announce support for Seaside application. The Magma souce repository now includes a 'Magma seaside' Monticello which allows a Magma repository to be used from a Seaside application. As a tutorial on how to modify a Seaside application to use Magma for persistance, a change set is provided which modifies Seaside's Sushi Store demonstration to store the inventory and orders in the repository. Please see http://minnow.cc.gatech.edu/squeak/5817 for details. Questions and comments are welcomed, preferably on the Magma mailing list. Regards Brent

1 0

new package structure
by Chris Muller 14 Nov '05

14 Nov '05

I want to try a new package structure without dependencies. The current versions of packages on SqueakSource are now individually loadable and saveable. To maintain one-click loading, there are new packages, MagmaTesterLoader, MagmaServerLoader and MagmaClientLoader. (I tried Configurations but they only save to HTTP repositories). - Chris

2 2

security advice
by Chris Muller 10 Nov '05

10 Nov '05

Magma must have security or it will never work directly on the Net. I hope KryptOn will prove a good basis for this, but I have reached a point where detailed choices have me struggling about where to balance transparency and security. For the most part, I have used the Croquet suggestions for my guide: http://minnow.cc.gatech.edu/squeak/3770. But let me draw attention to my specific matter of contention. "- Security needs to be largely invisible. The Diablo trading system, referred to in earlier email, points the way.." and, "I would suggest going with a system that always encrypts automatically to see how you like it. Even if you decide to build in a way to circumvent encryption from the first day, I would urge, on my knees, that sending data unencrypted require an explicit and highly visible coding change such that the default, easiest path to communication is indeed encrypted, and both original programmers and later reviewers can immediately spot digressions from the secure communications. I have a number of tragi-comic stories about people who knew they were using strong encryption ... except they were actually sending cleartext. Perhaps the requirement should be, do not add to the collection of funny stories :-)" Now, I searched for info about Diablo II's trading system but couldn't find any details; just stuff about the "paladins" and "mages" and stuff.. Anyone know where a good description of their trading system? Notwithstanding that, I am specifically torn on the idea of "always on" security because, ultimately, requiring the user to say, "useSecurity: false" is where the transparency ends. However maybe not. Maybe the user assumes POLA, since maybe what they expect by transparency is "the computer reasonably takes care of me as best it can even if I all I do is take care of my physical computer.". To put it in Magma terms.. Every repository created will require Capabilities to access it. Now, if you don't want to deal with security at all, it can put these capabilities in the default directory automatically. This is essentially laying the golden key right on top of the treasure chest, but it seems merely to extend the non-secure area from the confines of the image to the physical computer. IOW, you could still expose the repository on the net and only you could access it. But to do that you need to remember to bring the Capabilities with you to connect remotely so some awareness of security is required anyway, its not fully transparent. So lately I'm thinking this attempt to eat my cake and have it too is fruitless. Either the user will have to be somewhat aware of security or there should probably be no security. I need to choose a more definitive philosophy: always on? default on, allow turning it off? default off, allow turning it on? Comments or advice greatly appreciated.. - Chris

4 6

Re: Magma missing dirty objects?
by Cees De Groot 10 Nov '05

10 Nov '05

commit: aBlock | result | self begin. result _ aBlock value. self commit. ^result ... and aBlock has a return. Bummer. shouldn't that be aBlock valueOnReturnDo: [self commit] or something? (hmm.. Squeak doesn't have that one.) Anyway, i'll rewrite my code but I really think that "commit: [^foo]" shouldn't fail in this way...

2 2

Re: Magma missing dirty objects?
by Cees De Groot 09 Nov '05

09 Nov '05

Hmm... just found a session in the pool that was at transaction level 8. Committing over and over again helped :) Back to the drawing board - I probably have a code error somewhere in the webrequest-handling-in-magma-transaction-wrapper

1 0

Magma missing dirty objects?
by Cees De Groot 09 Nov '05

09 Nov '05

Hi, I am playing with storing Gardner pages in Magma. However, Magma doesn't seem to want to store stuff... I get it to store the very first transaction as far as I can determine from the disk file, but nothing else. If I reuse existing sessions, everything appears normal but if I get a new session it's initialized from disk and I get a freshly initialized data structure (a wiki with a default front page). Are there circumstances where Magma can miss dirty objects? The structure looks roughly like: root: aDictionary 'CamsWikis': aDictionary 'CamsWebsite: aCamsWikiStorage pages: aDictionary 'Welcome': aGSPage ... editions: anOrderedCollection 1: a GWEdition updating a wiki page is done by adding an edition. I'll keep looking for something obvious, in the meantime :)

1 0

Re: Magma + Seaside
by Chris Muller 28 Oct '05

28 Oct '05

This will be fun. There is no one with your experience using M+S, and I'll be glad to learn more about Seaside, thanks! I do hope the demo may afford the use of a MagmaCollectionReader somewhere in the inventory model; a great opportunity to demonstrate how they are used. Need some way to deliver a nice sampling of SushiProducts; hardcoded or require user to enter? I will brush up on Seaside. - Chris --- Brent Pinkney <brent.pinkney(a)aircom.co.za> wrote: > Hi Chris, > > In reply to your mail regarding a demonstration of Magma + Seaside, I > would advise just installing Seaside and going through the sample > applications - they install out the box. > > The most complex example is an online sushi shop. > > Seaside allows for customisation of its session class to allow the Seaside > session to open a database connection. It is this functionality I would > like to demonstrate. > > Seaside's BIG IDEA is to use continuation to manage state between http > requests. A very nice use of this is to page though a collection of > objects. > > Finally I would like to demonstrate the ability to modify the sushi bar's > inventory when a purchase is made. > > I suggest we make a monticello which modifies the Seaside demo accordingly. > ..

3 6

[ANN] Lava-brp.27
by Brent Pinkney 27 Oct '05

27 Oct '05

Hi, I have just release a new version of Lava and its test suite. This version allows the Lava code generator to be tested with and without optimisation. This isolated a few bugs in the previous version. The next version will fix the 2 failing test cases. -- Brent Pinkney Aircom International (SA) cell: +27 83 518 4167 tel: +27 11 324 3615 fax: +27 11 784 8027 e-mail: brent.pinkney(a)aircom.co.za

2 1

Enhancements 2 - with cs
by Brent Pinkney 27 Oct '05

27 Oct '05

Hi Chris, I anticipantion of our Magma + Seaside demo, could you concider adding the following changes to an official version of Magma. We have spoken about these changes before. The only note worthrthy change is ByteString>>alphabeticalNext. It is essential for read:from:upTo: as we have previously discussed. Cheers Brent -- Brent Pinkney Aircom International (SA) cell: +27 83 518 4167 tel: +27 11 324 3615 fax: +27 11 784 8027 e-mail: brent.pinkney(a)aircom.co.za

2 1

Enhancements
by Brent Pinkney 26 Oct '05

26 Oct '05

1 0

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

Magma