Preventing execution of a method

[Bruno Desthuilliers]

Emanuele D'Arrigo a écrit :
> On Dec 11, 7:48 pm, Bruno Desthuilliers
> <bdesth.quelquech... at free.quelquepart.fr> wrote:
>>> or to provide read-only
>>> access. I.e. right now I'm working on the graphical client which
>>> potentially could be rewritten entirely by the users. It is necessary
>>> and perfectly reasonable for the client module to access some of the
>>> objects to be represented graphically, but those objects shouldn't be
>>> modifiable by it.
>> Why so ? At worst, they'll break everything.
> 
> -IF- the application was single-user yes, it wouldn't be a big deal.
> But as it is potentially multi-user, I don't want one party to corrupt
> the application for everybody else.

A multi-users application with a GUI usually implies that it's a 
client-server app with the GUI deployed is on each client and the domain 
logic hosted on the server.