RE: [Openjmx-devel] RMI adaptor and remote notifications

[Bordet, S. <Sim...@co...>]

Hi,

> Regarding your question about=20
> filtering at server or client side, I guess both would work.=20
> The lookup=20
> service in service handles that by saying that this is up to=20
> the client.=20
> So all notifications are sent and filtered on the client side.=20

So, only one should work: client side filtering ;)

> The=20
> problem with this scheme is that you should try to send some=20
> few times=20
> the notification (there might be a network congestion for=20
> example) if it=20
> does not work the first time. The call should be threaded too=20
> because we=20
> do not want to block the server while calling the client.=20

No, I do want. At least must be sequential the call for filtering and =
notification...
Actual implementation is in same thread however: for server there is no =
difference between local and remote (I know, I know... :)

> Like for a lot of RMI application, I think that OpenJMX=20
> should run under=20
> a security manager (the RMI one would be fine) and a=20
> well-secured policy=20
> file.

Yes.

> We know from where are coming classes (with the help of codebase=20
> annotations) so why not simply add a sort of firewall? We=20
> could say that=20
> we accept for examples classes coming from location A and B.

No, this will be done by the policy file. The real problem is that the =
JMX security has totally been forgotten. If a JMXPermission must be =
needed to install an MBean, then things would be simpler.

Simon