Edit report at http://pecl.php.net/bugs/bug.php?id=8690&edit=1
ID: 8690
Updated by: [EMAIL PROTECTED]
Reported By: simonslaws at googlemail dot com
Status: Assigned
Id: 8690
Type: Bug
Package: SCA_SDO
Operating System:
I appears the RSS binding unintentionally made its way into the 1.2.1
release. This code is prototype and not intended for production use.
I've updated MakePackage.php in DUNLIN to exclude RSS from future
releases.
If anyone's interest in this RSS prototype drop a note here and I'll
happily answ
I've added bullets for eBay caching to improve performance and to add
the eBay binding to the release (we shouldn't put the binding into the
release without the caching). I've also added a note to remove RSS
from the release.
Graham.
On 14 May, 12:03, [EMAIL PROTECTED] wrote:
> I've created thi
How to find the current development branch
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"phpsoa" group.
To post to this group, send email to phpsoa@googlegroups.com
To unsubscribe from this group, send email to [
(Joining this thread a week late :-))
Mike, you have done a fantastic job of researching the options. I'm
puzzled why you say _two_ options: isn't there just one surviving
idea, which is what you and Graham have converged upon, the use of the
pipe symbol for both @param and @return, as in:
Mike Caplan (in pecl bug #10994) has raised the question of whether,
when a business exception is raised in a component that has been
called remotely - through a web service, say - the exception should be
serialised and flowed back, then deserialised and rethrown in its
entirety on the calling end
Hi Matthew,
I guess I am a little confused about the # notation that Graham outlined
(and wondered if that was just a slightly different way to handle the
problem). Am I correct that Graham is getting at a new notation for
specifying elements from a schema?
IE:
@return element http://Schema_N
