On Fri, Nov 27, 2009 at 10:44, panyasan <[email protected]> wrote:
>
>
> Yes, this is certainly the way to go. No matter how the backend is
> functioning internally, the behavior should be exactly the same from the
> perspective of the qooxdoo (or any other javascript-based) application on
> the client. And this is why a test suite like RpcExample is so important.
> This is what we should concentrate on and where I think all backend
> implementators can agree on. Your server-writing-guide
> (http://qooxdoo.org/documentation/0.8/rpc_server_writer_guide) should be
> the
> basis of that.
>
I had mis-remembered the name. Yes, that's what I referred to when I
discussed the Developers' Guide.
>
> Here are some suggestions:
>
> - The "Server writer guide" should be made a "Standard"
> - There should be a clear normative "core" (obligatory to pass the
> standard)
> and optional "extensions"
> - We should create a page with "proposals" to this standard (core /
> extensions) and then discuss the pros and cons of the proposals together.
>
Sounds fine. The normative "core" is, I think, what's currently in that
document, with the possible addition of:
>
>
> Derrell Lipman wrote:
> >
> > There is certainly room for expansion of the original "specification" in
> > the
> > Developers' Guide, and introspection is a very reasonable addition. Since
> > all of the key players are involved in this discussion already, you might
> > describe what you've implemented in that regard in the PHP backend to see
> > if
> > it is feasible to implement in the other backends.
> >
>
> I would do that as an extension proposal. However, there should be one
> "core" feature that allowed to query the server whether a certain extension
> is available.
>
Agreed. A qxServer.hasFeature(String featureName) method or something of
that sort would be appropriate I suppose. We might end up with other
qxServer.* methods, such as the introspection. (I'm not at all wed to that
name nor even to containing them in a single Class (in PHP terminology. We
can discuss how to make the hasFeature request.)
Derrell
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel