Dashboard > PHP Community > ... > SCA with PHP > SCA Wish List
Log In   View a printable version of the current page.
SCA Wish List
Added by Simon Laws, last edited by Matthew Peters (IBM) on Jun 10, 2008  (view change)
Labels: 
(None)


This is NOT a project plan. This is just a tentative list of tasks that people have raised for discussion.

Here is the latest futures list (aka wishlist) at November 2007:

Mostly done enough coding for a while but there are still some juicy areas:

Bindings

  • The ATOM binding is a long way from finished
  • Likewise RSS
  • JSON-RPC remove the reliance on CURL and replace with PHP streams.
  • Lots of interoperability issues when communicating with either big-SCA i.e. Java SCA or with non-SCA web services, atom feeds etc.

Other functional aspects

  • Security - describing the intent (confidentiality, authentication, etc.) in annotations
  • Support for https (suggested on more than one occasion but most recently by Rob Richards in a note to Matthew Peters. 15/2/07

Non-functional aspects

  • Performance, in particular the performance of the XMLDAS. At the moment we read, parse and interpret the same XML schema files over and over again. We would like to cache the model that we build inside the php_sdo extension, but although in discussions on the google group we have specified how it should work, have never implemented it.

New directions - these were futures last year too!

  • Single place for configuration and wiring - override annotations from an ini file?
  • Handle complex types without schema - something based on PHP classes perhaps

Areas we never got quite right

  • Reliable end to end flows for exceptions for all bindings: when an error occurs at the end of a chain of requests it can be hard to track; the text does not always find its way back to the invoking program. For example, sometimes error messages end up in WSDL files.
  • Ensure that as far as possible the exceptions thrown for errors are consistent across the bindings.
  • Configureable caching of where the wsdl, smd is written. At the moment these may just be dropped in the same directory as the php component itself, and in general this may not be writeable.
  • We currently derive the service location (URL) that we put in the wsdl by looking at how we were invoked. However, this may be misleading - we may be behind a firewall or router and we are just getting locally known names. The real service location may just not be computable, so we need to enable it to be specified by hand.

Please don't hesitate to volunteer for anything you would like to work on.

Powered by Atlassian Confluence, the Enterprise Wiki. (Version: 2.4.5 Build:#708 Apr 12, 2007) - Bug/feature request - Contact Administrators