On Dec 12, 9:09 am, Bruno Desthuilliers <bruno. [email protected]> wrote: > Emanuele D'Arrigo a écrit : > > > On Dec 11, 7:48 pm, Bruno Desthuilliers > > <[email protected]> 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.
This is assuming the 'BAD GUY' does not have access to the server code, right? -- http://mail.python.org/mailman/listinfo/python-list
