On Fri, Sep 19, 2008 at 4:12 PM, William Becker <[EMAIL PROTECTED]> wrote:
> There is no reason why we can't support both callbacks at the start and at
> the end (although we should use only one; we should either throw an
> exception or explicity say that in this case either the first or last is to
> be used).
>
I guess for that matter, the callback could be anywhere in the arg list...
(kind of like LocalArgResolvers?) and the method call would just check every
arg to see if it's a function and if it is, make it the callback...
If we are really going to stop supporting synch calls though, wouldn't it
make the code a little bit cleaner and sleeker if it was always in one
position?
Another option is to use a json format... something like:
jabsorb.service({cb: function(r,e) {}, args: ['a', 'b', 'c']});
Although that might be going too far. I see a lof of that kind of thing in
ExtJS, and it's growing on me... This might also might fit in with some of
the JSON-RPC 2.0 stuff (named parameters, etc.)
_______________________________________________
Jabsorb-dev mailing list
[email protected]
http://lists.jabsorb.org/mailman/listinfo/jabsorb-dev
