[Pier] State of persistency ?

Hi,

what is the state of the persistency layer in Pier ? What is implemented
and what is not ?


Thank you


Damien

_______________________________________________
SmallWiki, Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki
_______________________________________________
Smallwiki mailing list
[hidden email]
http://impara.de/mailman/listinfo/smallwiki

Dear Damien,

I am also working on the persistency issue, I need something working
well as soon as possible. Content authors for my site are nagging me
already, we go live in October.

I figured that magma was at least worth a try. As as DB it is all in the
smalltalk image without any dependency upon external servers. Magma
appears to be aiming to make persistency as simple as possible. Raw
performance is unlikely to be an issue for me. It seems like the right fit.

 I would have had something working by now if it were not for my windows
installation taking a dive due to disk errors. I am now up and running
again (just about). In the next couple of days/weeks I should have
something to show for my troubles.

If you want to try magma with seaside there are some updates/bug fixes
around (email me or, check recent history of the magma list  because the
repository has yet to be updated)

best regards

Keith

       
       
               
___________________________________________________________
All new Yahoo! Mail "The new Interface is stunning in its simplicity and ease of use." - PC Magazine
http://uk.docs.yahoo.com/nowyoucan.html

_______________________________________________
SmallWiki, Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki
_______________________________________________
Smallwiki mailing list
[hidden email]
http://impara.de/mailman/listinfo/smallwiki

Hi Keith,

Keith Hodges wrote:
> I am also working on the persistency issue, I need something working
> well as soon as possible. Content authors for my site are nagging me
> already, we go live in October.
>
> I figured that magma was at least worth a try. As as DB it is all in the
> smalltalk image without any dependency upon external servers. Magma
> appears to be aiming to make persistency as simple as possible. Raw
> performance is unlikely to be an issue for me. It seems like the right fit.
> [...]

In fact, my Pier setup is meant to be used for a static website with
very rare modification and by only one person. I don't think I need
magma at all, but thank you for the proposal.


Bye

_______________________________________________
SmallWiki, Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki
_______________________________________________
Smallwiki mailing list
[hidden email]
http://impara.de/mailman/listinfo/smallwiki

> In fact, my Pier setup is meant to be used for a static website with
> very rare modification and by only one person. I don't think I need
> magma at all, but thank you for the proposal.

My personal website has exactly the same requirements: mostly static,  
rare modification, editing only by one person (me).

I just save the image after changes.

Lukas

--
Lukas Renggli
http://www.lukas-renggli.ch



_______________________________________________
SmallWiki, Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki
_______________________________________________
Smallwiki mailing list
[hidden email]
http://impara.de/mailman/listinfo/smallwiki

Hi Keith

I would really be interested to learn more about it.
I thought that using a changeset-like mechanism for a domain that is  
open (and can be extended)
is a problem and may break the restoring facilities.

I was thinking that we could at least save the page in XML or a  
similar format after each command.
and we could recover the lastest changes.

Will you publish and share your code?
I would love to get a Smallwiki version whose image could get  
corrupted and that I could reconstruct :)

Stef


_______________________________________________
SmallWiki, Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki
_______________________________________________
Smallwiki mailing list
[hidden email]
http://impara.de/mailman/listinfo/smallwiki

Hi,

> I was thinking that we could at least save the page in XML or a  
> similar format after each command.
> and we could recover the lastest changes.
Do you know Thomas Froeb's PRXMLPersistency? You can get it at
http://source.impara.de. I use it for a project wiki and it works quite
fine. There are some problems when restoring an old version when a page
title contains a german umlaut like ä.
That Persistency module stores all data in XML-files, every version in a
seperate one.

Greets,
  David

_______________________________________________
SmallWiki, Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki

_______________________________________________
Smallwiki mailing list
[hidden email]
http://impara.de/mailman/listinfo/smallwiki

Interesting. How does it version the changes in the tree, e.g.  
deleting, moveing, copying, renaming pages? Is it open-source?

Lukas

--
Lukas Renggli
http://www.lukas-renggli.ch




_______________________________________________
SmallWiki, Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki

_______________________________________________
Smallwiki mailing list
[hidden email]
http://impara.de/mailman/listinfo/smallwiki

>> [PRXMLPersistency]
> Interesting. How does it version the changes in the tree, e.g.  
> deleting, moveing, copying, renaming pages?
There is a folder structure representing your page tree; each non-leaf
page is a folder. In those folders, there are the files for the leaf
pages. The filename is [version]-[page title].xml, eg. 4-myPage.xml.

I have not have a closer look on it, I've just started using it..
Moved pages still have a file/folder at their old location, but also a
new one at the new. The version number ist higher at the new one, of
cause, so that the most recent version could be identified.

There is no auto-versioning, too. That means you have to call
kernel persistency snapshot manually. The "recent changes" page does
display the changes only up to the last shapshot, when creating a new
one, all pages are displayed to be changed at that time.

Greets

_______________________________________________
SmallWiki, Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki
_______________________________________________
Smallwiki mailing list
[hidden email]
http://impara.de/mailman/listinfo/smallwiki

Staring at the code I want to override PRKernel>>critical:

PRKernel>>critical: aBlock

PRKernel persistency critical: aBlock

----

PRNullPersistency>>critical: aBlock

self kernel mutex critical: aBlock

----

so that when I subclass persistency I can nicely inform the database of
the changes

PRMagmaPersistency>>critical: aBlock

session commit: [ self kernel mutex critical: aBlock ]

-----

I know there is provision for over riding Persistency>>log: etc.

Is my plan ok or would it be considered bad style?

Keith






               
___________________________________________________________
All New Yahoo! Mail – Tired of Vi@gr@! come-ons? Let our SpamGuard protect you. http://uk.docs.yahoo.com/nowyoucan.html

_______________________________________________
SmallWiki, Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki

_______________________________________________
Smallwiki mailing list
[hidden email]
http://impara.de/mailman/listinfo/smallwiki

I am going for a rewrite of

PRCommand>>execute
 
    self isView
        ifTrue: [ self shouldNotImplement ].
    self kernel persistency critical: [           "changed to go via
persistency"
        self doValidate; doExecute.
        self isLogged
            ifTrue: [ self doPersistency ] ].
    self doAnswer

PRPersistency>>critical: b

kernel critical: b


Lukas, is that a change that would make it into the main stream?

Keith

               
___________________________________________________________
Inbox full of spam? Get leading spam protection and 1GB storage with All New Yahoo! Mail. http://uk.docs.yahoo.com/nowyoucan.html

_______________________________________________
SmallWiki, Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki
_______________________________________________
Smallwiki mailing list
[hidden email]
http://impara.de/mailman/listinfo/smallwiki

> Lukas, is that a change that would make it into the main stream?

I see, this completely makes sense. Please commit.

Lukas

--
Lukas Renggli
http://www.lukas-renggli.ch



_______________________________________________
SmallWiki, Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki
_______________________________________________
Smallwiki mailing list
[hidden email]
http://impara.de/mailman/listinfo/smallwiki