Pluggable state transfer factory

[ben.wang]

During the creation of the new package name for PojoCache, I have noticed that currently the state transfer code has direct coupling to PojoCache class. This is needed such that PojoCache needs to treat the state transfer differently (becuase of _JOBSS_INTERNAL_ region, e.g.).

I have discussed with Brian. We think the best way is to create a pluggable state transfer factory exposed from the new SPI. Any thought?

[manik]

What are you proposing, a getStateTransferGenerator() method on the SPI?

[brian.stansberry]

There is a JIRA related to this http://jira.jboss.com/jira/browse/JBCACHE-465. IMHO the right way to do this is to refactor out all the state transfer code (e.g. _getState and _setState)) into some sort of pluggable state transfer manager not just change how the factory is retrieved. Then PojoCache can have complete control.

This task still says 2.0 -- I thought it was moved to 2.1 as its an internal thing. But for Ben's needs it looks like it needs to be 2.0 anyway.

[ben.wang]

Yes, we will be using SPI, then I need the API to overload the state transfer code.

[manik]

This task still says 2.0 -- I thought it was moved to 2.1 as its an internal thing. But for Ben's needs it looks like it needs to be 2.0 anyway.

Will you be able to do this in the 2.0.0 timeframe? I hope to release an alpha by the end of the month.

[ben.wang]

We can sync up on this. It depends when to migrate the SPI. I am hoping to do it in 2.0 that way if we need to modify any part API we still can. I will need about one week after your finish the API and SPI codes. I have created a Jira to track this effort:

http://jira.jboss.com/jira/browse/JBCACHE-685