The lawsuit was brought past German royalties collector GEMA, who called on the Regional Court in Hamburg to organization the march hosting usage to a halt it from hosting 5,000 music tracks on its put for download.

GEMA released a report in German addressing the court’s ruling:

“The judgment states that the hosting service itself is now chief as a service to making persuaded that not any of the music tracks worried are distributed via its programme in the future. This means that the copyright holder is no longer required to perform the ongoing and complex checks.”

The court concluded that Rapidshare and other like queue sharing sites had not infatuated the proper measures to impede copyright infringement from occurring via the service

aRoot linkToStyle:

Use this instead:

aRoot stylesheet url: ‘/main.css’.

aRoot linkToStyle: ‘/main.css’

does not work in Seaside 2.8, try

aRoot stylesheet resourceURL ‘/main.css’

instead if using this version.

This article is IMHO good example of Seaside’s AJAX capabilities, but as a lot of people tends to copy code without thinking I tried to warn them so they wouldn’t have to learn all that the hard way (which, OTOH, migh be better at times).

“Lazy initialization is pointless here. Use it in cases where the performance hit of allways having to send a ifNil: message overcomes the odds of having a large/long initialization deffered until needed” -> “Lazy initialization is pointless here. Use it in cases where the performance hit of _allways_ having to send a ifNil: message is neglectible in comparation with large and not everytime needed allocation (or if it speeds up startup of your application)” (WTF i was trying to say here ?

The memento pattern however is useful to investigate as it has many potential applications. The decision to use an “optimistic” update approach as outlined in the tutorial vs a “pessimistic” approach as you describe is not a “one size fits all” question. It is dependent on your persistence mechanism and your performance requirements (E.g. the cost of rollback vs the cost of commit)

Lazy initialization is a bit of a personal preference of mine – I cannot remember a single case in any of my apps where the added cost of the #ifNil:has been significant whereas I have hit problems on a number of occasions with badly performing #initialize methods. I sure other may have anecdotes that lead them to prefer the opposite approach

You will note that I did provide #addContact: method on MyAddressBook in Session 1 (I left #removeContact: out of scope for the tutorial). You are correct that there are dangers *if* you can’t trust your clients to use the promoted interface on the containing class but there are an equal number of dangers with always return a copy of a collection (profusion of object references, inconsistent state etc.)

Either editing the copy, or even better using the method Michel B. suggested seems as a better alternative to me – WARenderCanvas responds to cancelButton, at least in 2.7a1-lr.139 I’m using.

Also, readers beware: This example answers a _reference_ to an collection used internally in a class. This is in many cases now what you want, as it can lead to unwanted side-effects. Preferred solution is ansvering a copy of the collection and delegating the needed functionality (ie. adding/removig etc.) as such:

“Lazy initialization is pointless here. Use it in cases where the performance hit of allways having to send a ifNil: message overcomes the odds of having a large/long initialization deffered until needed”
contacts
^ (contacts ifNil: [contacts := OrderedCollection new]) copy

addContact: aContact
contacts add: aContact

remove: aContact
contacts remove: aContact

This sounds very useful but I can’t find an implementation of #cancelButton on WARenderCanvas. Is this an extension you have written or am I missing something?