On Sep 29, 8:47 am, mario ruggier <[EMAIL PROTECTED]> wrote: > On Mon, 29 Sep 2008 07:57:49 -0700 (PDT), Jonathan Vanasco > > <[EMAIL PROTECTED]> wrote: > > > would you want a desktop client to have 'all' operation and access to > > the objects methods and fields? > > In principal, no; only an explicitly exposed subset. > > But, in practice, and as I am only just mentally exploring this idea, I do > not really care if the exposing mechanism forces that all attributes and > methods be exposed -- some way to limit that can always be layered on top > later. > > Similarly, for the sake of toying with the idea, the many security issues > may just be ignored. Note that the client may be any that supports rpc, so > it could be desktop just as well as web. > > But, what makes think that this difference is important? > > mario
I have some Big Ideas on this, but don't have time to write about it now. Basically, I envision a RESTful M(V)C/AJAX facade where all the AJAX (or RPC, if that's what yer into) calls are encapsulated in JS classes. There would also be JS model classes, which for the most part, I think, could just be simple data containers (with capability to do much more if needed). I've started to implement something along these lines in the latest version of a project I'm working on. If I get it into some kind of usable state, I'll share it. At one point, I thought I saw a project working on something like this, but I can't find it ATM. -wlb --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
