After a short look at the documentation, I wanted to ask, if the
Client-side API should really be so complex? :)
For me it is a little bit hard, that for just retrieving a value from my
cache:
DirectMemoryCacheResponse<Wine> response =
client.retrieve(
new DirectMemoryCacheRequest().setKey( "bordeaux" )
.setSerializer( SerializerFactory.createNewSerializer() )
.setExchangeType( ExchangeType.JSON )
.setObjectClass( Wine.class ) );
I think for the client-side it should be transparent, if you are using a
local or a remote cache.
Means: the complexity should kept from the client. the client should use
the CacheService-Interface
WDYT? :)
(JAX-RS client api? jersey / cxf client api? :))
2012/2/21 Olivier Lamy <[email protected]>
> 2012/2/21 Raffaele P. Guidi <[email protected]>:
> > And is there already a schedule? I sometimes hang in paris (my employer
> is
> > a french bank) and could have some meeting in that period
>
> AFAIK not yet.
>
> >
> > On Mon, Feb 20, 2012 at 3:55 PM, Benoit Perroud <[email protected]>
> wrote:
> >
> >> > can you please share more devoxx details please? I could come to
> Paris!
> >>
> >> Devoxx France is a sort of clone of Devoxx, but localized, i.e. most
> >> of the presentation will be in French.
> >>
> >> We will present DM under the Tools in Action topic. I still don't know
> >> precisely what will be in the presentation, but I will work hard the
> >> two next monthes to be able to show something impressive :)
> >>
> >> For more details (but again, in French) you can check the web site :
> >> http://devoxx.fr
> >>
> >> If some of you plan to come we could try to organize a DM meetup at
> >> the same time
> >>
> >> Cheers,
> >>
> >> Benoit.
> >>
>
>
>
> --
> Olivier Lamy
> Talend: http://coders.talend.com
> http://twitter.com/olamy | http://linkedin.com/in/olamy
>
--
Viele Grüße/Best Regards
Daniel Manzke
