On Wed, Jun 6, 2012 at 10:08 AM, Anoop Sam John <[email protected]> wrote: > Mean while Andrew I have just seen that in trunk the interface > InternalScanner is marked as private [@InterfaceAudience.Private] > Through the CP it is exposed now right. And the above use case need customer > to implement this also. What about marking this Public?
It is always going to be the case that CPs will require access to internals. That doesn't mean the APIs they use should be marked Public, an exception being the CP framework APIs themselves. InternalScanner should remain Private IMHO, it's in the name. :-) Best regards, - Andy Problems worthy of attack prove their worth by hitting back. - Piet Hein (via Tom White)
