Thanks Philippe
yeh i undestand how the meta-descriptions for an object are built.
it makes sense to use the solution you propose, however i dont want to get rid of the cache, i like the idea of keeping a cache of built descriptions for an object and each time new code is deployed the cache has to be manually flushed, by calling #flush on the default instance of MADescriptionBuilder.
Dale is going implement SystemChangeNotifier soon for, so we can always allow MADescriptionBuilder to subcribe to systemEvents later.
Does that sound reasonable ?
PS: looking at the squeak implementation it seems that MADescriptionBuilder flushes its cache of description if any method is changed or modified or added in the entire System, not necessrily an object in the MADescriptionBuilder cache > Date: Wed, 10 Oct 2007 06:48:18 +0200> From: philippe.marschall(a)gmail.com> To: cappadonza(a)hotmail.com> Subject: Re: [GS/SS Beta] [betaG/S] SystemChangeNotifier> CC: beta(a)seaside.gemstone.com> > 2007/10/9, isaiah perumalla <cappadonza(a)hotmail.com>:> >> > in squeak there is a class ystemChangeNotifier, what is the equivalent of> > that in Gemstone/S> > I don't think you necessarily need one. Some background:> To build a metadescription of an object Magritte per default only> looks a the class side. It collects all the selectors the class of the> object contains that begin with 'description' and performs them. This> can take a moment on Squeak so a cache was added that maps classes to> metadescriptions. This cache will have to be invalidated if a class is> changed (a method added or removed).> > A solution for this would be to make a MADescriptionBuilder for use in> production, this one would not be invalidated automatically. You would> have to invalidate it whenever you deploy code. It might be that> building metadescriptions of GemStone in fast enough and you don't> need any cache.> > Cheers> Philippe> > > ________________________________> > Sell your car for just $30 at CarPoint.com.au. It's simple!
_________________________________________________________________
It's simple! Sell your car for just $30 at CarPoint.com.au
http://a.ninemsn.com.au/b.aspx?URL=http%3A%2F%2Fsecure%2Dau%2Eimrworldwide%…
hey guys
In Magritte in MAObjectTest class there is a method #testReferenceStream
which basically ensures every object is serializable and after the object is
deserialized, the original and serialized object are equal but have
different references. (ie serialized object is a copy of the original
object).
In Magritte what and where is object serialization used for ? so i can get a
better understanding on how to test this in GemStone/s
thanks
Isaiah
--
View this message in context: http://www.nabble.com/Magritte-object-serialization--testReferenceStream-tf…
Sent from the SmallWiki mailing list archive at Nabble.com.
Hello,
I have a settings model which initializes from description defaults and
keeps its values as a properties dictionary. If when coding I happen to
change or remove a description, when I edit and save the settings the
stale description still remains in the properties dictionary.
I am looking for a hook with which I can tell the Memento, to clear the
old settings and write the new ones. Is there such a thing?
For example if the model knew it was about to be saved to it could clear
out/reset its values in anticipation.
best regards
Keith
I have attempted to use the MAFileUploadComponent slightly more manually
than usual.
e.g.
getComponent
^ widget childrenCache at: {item. field} ifAbsentPut: [
(field componentClass
memento: (MAStraitMemento model: item description:
field)
description: field
parent: widget).
].
However, the value returned to the callback is the filename string,
rather than the file itself. I feel I am missing something somewhere,
any ideas what it might be?
Keith
Hi,
I am building a site using Pier and I have the following problem
related to user rights. The explanations are rather long.
I have two groups of users:
- admins - An admin can do anything, including changing rights.
- editors - An editor can only Edit, Move, Remove, Add, Copy and Logout.
I have two users (and will have more in the future):
- admin - belongs to both the admin and editors groups.
- editor - belongs to the editor group.
I created 2 Commands components and embedded both in the page:
- completeCommands - this component include all commands. It has the
following rights:
owner mode: --aaa-ccccemrsv
group mode: --aaa-ccccemrsv
other mode: --------------v
owner: admin
group: admins
- editorCommands - this contains only the editor commands. It has the
following rights:
owner mode: --aaa-ccccemrsv
group mode: --aaa-ccccemrsv
other mode: --------------v
owner: admin
group: editors
When I login as admin, I see both components, as I expected. The
problem is that when I login as editor, I only see the Logout command
from the editorCommands. What am I doing wrong?
Cheers,
Doru
--
www.iam.unibe.ch/~girbawww.iam.unibe.ch/~girba/blog/
"Problem solving efficiency grows with the abstractness level of
problem understanding."