Re: proposal: Clusterable instead of Serializable

[Eelco Hillenius <ee...@gmail.com>]

I just committed the changes for the core projects (both the 1.3
branch and 2.0 trunk). See
http://issues.apache.org/jira/browse/WICKET-337

So Eugene, this configuration fragment:

<include>
  <class-expression>wicket.IClusterable+</class-expression>
  <honor-transient>true</honor-transient>
</include>

should suffice for Wicket, right? Pretty cool if that works! Could you
ping this thread when you made some progress?

Cheers,

Eelco


On 2/28/07, Eelco Hillenius <ee...@gmail.com> wrote:
> Hi,
>
> I'm making an inventory of classes that should be instrumented by
> Terracotta if you deploy for them. I have a whole bunch of classes and
> interfaces like PopupSettings and IPageable and IPagingLabelProvider
> that are serializable which typically means in the context of Wicket
> that they should be available for serializing. Now, just telling
> Terracotta to instrument everything that implements Serializable isn't
> gonna work as that is way to course and touches classes outside the
> scope of Wicket easily (think of all the hibernate classes etc you
> might use).
>
> I'd like to propose introducing an interface like 'Clusterable' that
> simply extends Serializable and replacing all the classes in Wicket
> that implement Serializable to implement that instead. Not only would
> that communicate our intend a little bit better, but it would also
> mean that we could just tell the Terracotta config file to instrument
> all implementations of that interface and be done with it. Thats
> easier to get to a good configuration for Terracotta now *and* if we
> keep on playing by those rules for the Wicket projects, we can
> refactor what we want without ever having to be worried about breaking
> a Terracotta configuration (not to mention having to maintain several
> versions of that configuration).
>
> Any grave objections to this? Eugene, will that work?
>
> Regards,
>
> Eelco
>

Re: [tc-dev] proposal: Clusterable instead of Serializable

[Eugene Kuleshov <eu...@terracottatech.com>]

Eelco Hillenius wrote:
> I just committed the changes for the core projects (both the 1.3
> branch and 2.0 trunk). See
> http://issues.apache.org/jira/browse/WICKET-337
>
> So Eugene, this configuration fragment:
>
> <include>
>   <class-expression>wicket.IClusterable+</class-expression>
>   <honor-transient>true</honor-transient>
> </include>
>
> should suffice for Wicket, right? 
  That is the idea.
> Pretty cool if that works! Could you
> ping this thread when you made some progress?
>   
  Will do. It might take longer then I though, because I had to do some 
additional refactorings of the surrounding code.

  regards,
  Eugene