On Sun, Nov 29, 2009 at 11:11, panyasan <[email protected]> wrote:
>
> Derrell Lipman wrote:
> >
> > - In the jsonrpc_extensions page, It's important, I think, to describe
> the
> > externally-visible operation of the extension in addition to how to test
> > whether the extension exists. As an example, let's say I see that there
> is
> > an extension for reflection. Great, I say, and I now know how to test
> > whether reflection is supported by the server, but not how to use the
> > reflection API, i.e. what methods are provided if this extension is
> > available, and what are those methods' signatures.
> >
>
> What about returning a property "specServices" which is an array of service
> names provided by the capability / feature? Then, if introspection is
> enabled, thes services can be further queried for method names and
> signatures?
>
That's not what I'm talking about. The server writer needs to know how to
implement a conforming implementation of the extension. Without looking at
the PHP server, I'd have no idea, currently, what the reflection API does or
how to implement the reflection API in my new server. The documentation for
an extension should, I think, include the name(s) of the method(s) that must
be implemented for a conforming implementation of that extension, and the
signatures of those methods. This is not a run-time issue, it's a developer
implementation issue, so specServices does not accomplish what I'm referring
to.
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
