river-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Michał Kłeczek <michal.klec...@xpro.biz>
Subject Re: River-436 - need some explanation of preferred class provider
Date Fri, 07 Mar 2014 18:02:32 GMT
Isn't InvocationHandler a "smart proxy"???
7 mar 2014 18:55 "Gregg Wonderly" <gergg@cox.net> napisał(a):

> Greg is referring to the fact that Jeri provides the ability to ship a
> java.reflection.Proxy object to the report host as the service
> implementation, instead of having to ship the actual class as a
> serializable endpoint.  This is a big difference.  Adding endpoint
> implementations into this is like apples and oranges.  Yes, if there is
> "code" needed, it needs to be downloaded.  But, dynamic proxies take away
> the need for code to be downloaded, unless you need a smart proxy.
>
> Gregg Wonderly
>
> On Mar 7, 2014, at 10:32 AM, Michał Kłeczek <michal.kleczek@xpro.biz>
> wrote:
>
> > Sure there is a need for code downloading for JERI proxies. You seem to
> assume
> > no custom endpoint implementations.
> >
> > There is really no difference between dynamic proxy and "normal" object.
> >
> > Regards,
> >
> > On Friday, March 07, 2014 09:32:04 AM Greg Trasuk wrote:
> >>
> >> Now, dynamic proxies are a different story, and JERI already uses the
> >> dynamic proxy mechanism.  There's no need, for example to download an
> >> implementation class for an object that is directly exported - you only
> >> really need the service interface to be available locally.
> >>
> >>
> >> Cheers,
> >>
> >> Greg Trasuk
> >
> > --
> > Michał Kłeczek
> > XPro Sp. z o. o.
> > ul. Borowskiego 2
> > 03-475 Warszawa
> > Polska<Michał Kłeczek (XPro).vcf>
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message