Re: [opensource-dev] The Faces Of Client-Side Code

2010-03-07 Thread Ricky
I agree 100%. Yet, as this topic is about the different faces of client code, having the terms well-defined will help in the future. We are both agreed that there are sandboxed and non-sandboxed parts, and each has it's purpose. I just wanted to establish common terms, with some generic examples

Re: [opensource-dev] The Faces Of Client-Side Code

2010-03-07 Thread Morgaine
User perceptions are completely orthogonal to the engineering issues here though, Ricky. We could certainly make all use cases look entirely uniform from a user perspective if we wanted to, but we don't advocate that because the security and responsibility issues are so different in the two (and o

Re: [opensource-dev] The Faces Of Client-Side Code

2010-03-07 Thread Ricky
Carlo, both you and Morgain make very good arguments as to why various parts I separated are, technically, the same. However, while I understand that Dynamic Scripts (loaded from serverside) and UserScripts are completely the same thing (just like in a browser, the JavaScript loaded from the serve

Re: [opensource-dev] The Faces Of Client-Side Code

2010-03-07 Thread Argent Stonecutter
On 2010-03-07, at 08:20, Carlo Wood wrote: > On Sat, Mar 06, 2010 at 11:19:43PM -0800, Ricky wrote: >> Client Plugins > Ok, although I'd prefer if-- for example-- media plugins run in a > sandbox; > think about the recent mention of the quicktime exploit. The kind of sandbox you can usefully en

Re: [opensource-dev] The Faces Of Client-Side Code

2010-03-07 Thread Carlo Wood
On Sat, Mar 06, 2010 at 11:19:43PM -0800, Ricky wrote: > Client Plugins Ok, although I'd prefer if-- for example-- media plugins run in a sandbox; think about the recent mention of the quicktime exploit. > Client Extensions - Interpreted code packages placed in a special folder in > the > client

Re: [opensource-dev] The Faces Of Client-Side Code

2010-03-07 Thread Morgaine
Ricky, there's nothing major wrong with your classification, but you make two breakdowns which actually have no clear demarcation between them: - Your "Client Plugins" and your "Client Extensions" are actually one and the same thing, merely representing two different use cases of the same

[opensource-dev] The Faces Of Client-Side Code

2010-03-06 Thread Ricky
A while back, before the 2.0 announce interrupted our conversation, I had made a post about what I saw as three different forms of client-side scripting/plugins/whathaveyou. I've since been convinced that I missed something. So here goes again, with a (hopefully) improved set of definitions: Cli