Nabble - SCA and SDO for PHP

Re: SCA services access control...?

2008-08-01T00:32:09Z

Hi Yannick, once again, apologies for not responding sooner.

Security is something which has come up on numerous occasions, but no
one has been able to find the time to incorporate something. I
believe unless you are able to do something that, sadly, this is still
the case. I've included a couple of links to previous discussions
[1,2].

I'm afraid don't fully appreciate the issues you are encountering, but
have some thoughts on the suggested design... I think modifying the
service interface to include security parameters does not seem like an
approach that fits with SCA. SCA tries to keep service interfaces
clean (focus on business interface) and consistent across protocols.
I think the security information more appropriately belongs in a
header, rather than on the service interface. I think using
annotations to control things is good, and if the configuration is
complex then an ini file approach like the ebaysoap binding can help
[3].

I hope this helps.

Regards, Graham

[1] http://groups.google.co.uk/group/phpsoa/browse_thread/thread/c92450e7a170a3e8/43f639a7b4f7af07?lnk=gst&q=Kieran#43f639a7b4f7af07

[2] http://groups.google.co.uk/group/phpsoa/browse_thread/thread/47d069e4ca44d9a9/aa11352d10c28e03?lnk=gst&q=Rob#aa11352d10c28e03

[3] http://osoa.org/display/PHP/eBay+SOAP+Binding+Documentation

On 30 Jul, 04:15, Yannick <ywarn...@...> wrote:

> Anybody got anything to say about this?
>
> On 27 juil, 20:11, Yannick <ywarn...@...> wrote:
>
> > Hi,
>
> > I think I mentioned it the first time I sent an e-mail on this list,
> > but one of the major problems I have with using SCA is that, if I do
> > implement it into existing classes, I don't want just anyone to be
> > able to use them freely.
>
> > In Dokeos (and outside of any web services context), we rely on an
> > initial authentication process (using sessions) to make sure the user
> > is authorized to do what he is trying to do.
>
> > However, if I want to take the full benefit out of SCA, I would like
> > to be able to re-use my existing functions and *just* add a few
> > comments here and there, and be done with it. Now the problem is that,
> > if I do that, I inevitably loose the "session" context (as I am going
> > through web services), and so I loose the authentication pre-check.
>
> > This is a big problem to me, as adding an authentication process
> > specifically for the web services, it means I *have to* reimplement
> > most of my functions to add an authentication layer.
>
> > I remember Caroline saying that someone was remotely working on/
> > thinking about the topic, but haven't seen any discussion about it
> > since then.
>
> > How are other people here dealing with that?
> > This is most likely to be the dead-end for us in terms of either
> > adopting SCA_SDO or at least considering it as a real benefit.
>
> > From the top of my head, I would say that if there was a way to
> > configure a web service transparently to work in an "authenticated
> > mode" and that, from there on, it always added a required "first"
> > parameter being a shared key, and optionally identified the source by
> > IP address, it would be enough.
>
> > Something like adding a parameter @security.shared_key ../mykey.php in
> > the class documentation, that would automatically:
> > - generate a modified WSDL that shows a shared_key param as a first
> > parameter for any function
> > - add a check of this first parameter before going through with the
> > answer to the service request
>
> > What would be the likeliness of that idea to be integrated into
> > SCA_SDO? We have plans for a release of our next Dokeos version at the
> > end of September. If it is likely, then how likely would it be that a
> > modified version of SCA_SDO can be rolled into PECL by then (because,
> > of course, we want our users to be able to use the feature without
> > having to pack SCA_SDO in our package)? As SCA_SDO is not written in
> > PHP, it would be difficult to me to contribute code, but I can
> > certainly contribute ideas, analysis and testing.
>
> > Yannick

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "phpsoa" group.
To post to this group, send email to phpsoa@...
To unsubscribe from this group, send email to phpsoa+unsubscribe@...
For more options, visit this group at http://groups.google.co.uk/group/phpsoa?hl=en
-~----------~----~----~----~------~----~------~--~---

Re: Possible to offer a service from a simple function?

2008-07-31T22:02:39Z

Thanks, I'll see what I can do, I'm also a little short on time (I
tend to work on things in peaks and then move on to other things, so
that'll have to wait until the next peak for now)

On 31 juil, 08:46, Graham Charters <gchart...@...> wrote:

> Hi Yannick,
>
> Apologies for not replying sooner. I'm swamped with other activities
> at the moment, so not able to contribute much :-(
>
> I think in principle there's nothing preventing a function being
> exposed as SCA component. This hasn't been done and I'm sure there
> would be devils in the detail around building up service descriptions,
> and so on. I believe ext/soap supports functions as service
> implementations so it should be possible to target them with
> @binding.ws.
>
> If it's something you'd be interested to work on, I'd be glad to help
> in what little time I can spare. In the absence of this support, I
> think wrapper classes is the only option, which I agree is not ideal.
>
> Sorry I can't be of more help.
>
> Regards, Graham.
>
> On 30 Jul, 04:25, Yannick <ywarn...@...> wrote:
>
> > Or actually I might use SCA, but will newly built methods, which kinds
> > of defeats half the purpose.
>
> > On 29 juil, 22:22, Yannick <ywarn...@...> wrote:
>
> > > I'd really like to get started soon on web services implementation,
> > > and the series of e-mails I have sent give a clear idea of my concerns
> > > regarding SCA. I won't lie, I'm currently looking at other projects
> > > because of the shortcomings I have found in SCA, which kind of sucks
> > > as I really liked the idea behind SCA (re-use of existing functions
> > > using PHPDoc comments). On the other hand, I really can't see how one
> > > could provide web services using existing functions if:
>
> > > - they absolutely have to use classes
> > > - the files must have the same name as the class inside (What if there
> > > are two classes inside? What if you have an existing open-source
> > > project with lots of files depending on your class?). Apparently there
> > > is no way either to include a class-definition file intp a placeholder
> > > file which holds the right filename (because of the time at which the
> > > inclusion statement is processed the comments are already gone).
> > > - there is no security check anywhere
> > > - a missing space or a minor difference in the PHPDoc format can break
> > > the parsing process
>
> > > Anyway, if it doesn't work out now, it might work out later. I'll try
> > > to assist in fixing all these little issues that make it very
> > > difficult to use for me (and in the meantime, I'll probably fall down
> > > to a PHP solution like NuSOAP or something of the likes).
>
> > > Thanks anyway,
>
> > > Yannick
>
> > > On 27 juil, 19:52, Yannick <ywarn...@...> wrote:
>
> > > > Hi there,
>
> > > > As I am trying out SCA, a bunch of questions come to mind. I'll try to
> > > > stick to one-question-per-mail for clarity and indexing of the
> > > > answers.
>
> > > > Following the documentation herehttp://www.osoa.org/display/PHP/SCA+Documentation#SCADocumentation-2:
> > > > "...PHP annotations are used to define PHP classes as SCA
> > > > components,...".
> > > > As far as I can see, there's no way to use a simple functions library
> > > > and provide web services from it, is there?
>
> > > > If not, considering a functions library should also use a file-level
> > > > header for PHPDocumentor, is there a particular reason why it is not
> > > > possible to use simple functions?
>
> > > > Thanks,
>
> > > > Yannick

Re: Possible to offer a service from a simple function?

2008-07-31T06:46:16Z

Hi Yannick,

Apologies for not replying sooner. I'm swamped with other activities
at the moment, so not able to contribute much :-(

I think in principle there's nothing preventing a function being
exposed as SCA component. This hasn't been done and I'm sure there
would be devils in the detail around building up service descriptions,
and so on. I believe ext/soap supports functions as service
implementations so it should be possible to target them with
@binding.ws.

If it's something you'd be interested to work on, I'd be glad to help
in what little time I can spare. In the absence of this support, I
think wrapper classes is the only option, which I agree is not ideal.

Sorry I can't be of more help.

Regards, Graham.

On 30 Jul, 04:25, Yannick <ywarn...@...> wrote:

> Or actually I might use SCA, but will newly built methods, which kinds
> of defeats half the purpose.
>
> On 29 juil, 22:22, Yannick <ywarn...@...> wrote:
>
> > I'd really like to get started soon on web services implementation,
> > and the series of e-mails I have sent give a clear idea of my concerns
> > regarding SCA. I won't lie, I'm currently looking at other projects
> > because of the shortcomings I have found in SCA, which kind of sucks
> > as I really liked the idea behind SCA (re-use of existing functions
> > using PHPDoc comments). On the other hand, I really can't see how one
> > could provide web services using existing functions if:
>
> > - they absolutely have to use classes
> > - the files must have the same name as the class inside (What if there
> > are two classes inside? What if you have an existing open-source
> > project with lots of files depending on your class?). Apparently there
> > is no way either to include a class-definition file intp a placeholder
> > file which holds the right filename (because of the time at which the
> > inclusion statement is processed the comments are already gone).
> > - there is no security check anywhere
> > - a missing space or a minor difference in the PHPDoc format can break
> > the parsing process
>
> > Anyway, if it doesn't work out now, it might work out later. I'll try
> > to assist in fixing all these little issues that make it very
> > difficult to use for me (and in the meantime, I'll probably fall down
> > to a PHP solution like NuSOAP or something of the likes).
>
> > Thanks anyway,
>
> > Yannick
>
> > On 27 juil, 19:52, Yannick <ywarn...@...> wrote:
>
> > > Hi there,
>
> > > As I am trying out SCA, a bunch of questions come to mind. I'll try to
> > > stick to one-question-per-mail for clarity and indexing of the
> > > answers.
>
> > > Following the documentation herehttp://www.osoa.org/display/PHP/SCA+Documentation#SCADocumentation-2:
> > > "...PHP annotations are used to define PHP classes as SCA
> > > components,...".
> > > As far as I can see, there's no way to use a simple functions library
> > > and provide web services from it, is there?
>
> > > If not, considering a functions library should also use a file-level
> > > header for PHPDocumentor, is there a particular reason why it is not
> > > possible to use simple functions?
>
> > > Thanks,
>
> > > Yannick

Re: Error with documentation example

2008-07-30T02:37:30Z

On 30 Jul, 04:11, Yannick <ywarn...@...> wrote:

> Thanks
>
> On 29 juil, 08:17, Graham Charters <gchart...@...> wrote:
>
> > Hi Matthew,
>
> > Thanks for making these changes. I was going to, but got derailed by
> > the fact that the first ones are in images. I see these haven't been
> > changed. I think Simon Laws created these and I don't have the
> > originals. If we can't get the originals we'll need to recreate them,
> > or remove the images.
>
> > Regards, Graham.
>
> > On 29 Jul, 11:03, Matthew Peters <matthew.f.pet...@...>
> > wrote:
>
> > > I just went through the page and changed all the binding.ws (and a
> > > couple of binding.wsdl) to binding.soap.
>
> > > I also sprinkled a warning that the most up to date documentation is
> > > on php.net through the document:
>
> > > || _The most up to date documentation is to be found on the php.net
> > > site, at [http://www.php.net/manual/en/book.sca.php] for example_ ||
>
> > > Matthew
>
> > > On Jul 29, 8:21 am, Graham Charters <gchart...@...> wrote:
>
> > > > Hi Yannick,
>
> > > > Thanks for pointing out the documentation problem on osoa.org. I'll
> > > > try to fix that shortly.
>
> > > > Dalibor is correct that WSDL is only generated for binding.soap.
> > > > Other bindings will generate their own kinds of service descriptions
> > > > where appropriate. For example, binding.jsonrpc with generate a
> > > > service method description if you add ?smd.
>
> > > > Regards, Graham.
>
> > > > On 28 Jul, 00:01, Dalibor Andzakovic <Dalibor.Andzako...@...>
> > > > wrote:
>
> > > > > Correct. WSDL only gets created for SOAP services AFAIK.
>
> > > > > dali
>
> > > > > -----Original Message-----
> > > > > From: phpsoa@... on behalf of Yannick
> > > > > Sent: Mon 2008-07-28 11:00
> > > > > To: phpsoa
> > > > > Subject: [phpsoa] Re: Error with documentation example
>
> > > > > Sorry, @binding.soap definitely works. I've been trying all the other
> > > > > types (atom, jsonrpc, message, restrpc, tuscany, ebaysoap, local,
> > > > > restresource, xmlrpc) but none of these generate a wsdl, even though
> > > > > they don't generate any error message either.
> > > > > Is that due to something proper to each of these other web services
> > > > > types?
>
> > > > > Yannick
>
> > > > > On 27 juil, 17:39, Yannick <ywarn...@...> wrote:
> > > > > > Like I said, finding the problem was not difficult nor long, but it's
> > > > > > still confusing that there is no explanation of what "ws" could be
> > > > > > replaced by in @binding.ws. Of course, replacing it by @binding.soap
> > > > > > worked immediately.
> > > > > > However, I tried to change it to @binding.restrpc and that,
> > > > > > apparently, brings me back to the initial state (blank page); but this
> > > > > > time I get no error report.
> > > > > > Changing it back to @binding.soap doesn't work.
>
> > > > > > Yannick
>
> > > > > > On 26 juil, 18:24, Yannick <ywarn...@...> wrote:
>
> > > > > > > Hi there,
>
> > > > > > > I'm currently taking my first steps with SCA-SDO following the example
> > > > > > > given here:
>
> > > > > > >http://www.osoa.org/display/PHP/SCA+Documentation#SCADocumentation-2.5
>
> > > > > > > I am using an Ubuntu 8.04 system ad I downloaded SCA_SDO using the
> > > > > > > PECL command line interface.
> > > > > > > Now I'm sure I'm going to find the problem soon, but as the
> > > > > > > documentation, as it is, is leading me to a problem and obviously I
> > > > > > > can't create and account to edit that page, I wanted to mention it.
>
> > > > > > > When I try getting the WSDL for that page, I get a (double) error
> > > > > > > message:
>
> > > > > > > [Sat Jul 26 11:58:27 2008] [error] [client 127.0.0.1] PHP Warning:
> > > > > > > SCA_Binding_Factory::require(SCA/Bindings/ws/RequestTester.php) [<a
> > > > > > > href='function.SCA-Binding-Factory-require'>function.SCA-Binding-
> > > > > > > Factory-require</a>]: failed to open stream: No such file or directory
> > > > > > > in /usr/share/php/SCA/SCA_BindingFactory.php on line 68
> > > > > > > [Sat Jul 26 11:58:27 2008] [error] [client 127.0.0.1] PHP Fatal
> > > > > > > error: SCA_Binding_Factory::require() [<a
> > > > > > > href='function.require'>function.require</a>]: Failed opening required
> > > > > > > 'SCA/Bindings/ws/RequestTester.php' (include_path='.:/usr/share/php:/
> > > > > > > usr/share/pear') in /usr/share/php/SCA/SCA_BindingFactory.php on line
> > > > > > > 68
>
> > > > > > > Looking into my /usr/share/php/SCA/ directory, I have:
>
> > > > > > > /usr/share/php/SCA/Bindings$ ls
> > > > > > > atom jsonrpc message restrpc tuscany
> > > > > > > ebaysoap local restresource soap xmlrpc
>
> > > > > > > So, no directory called "ws/". I guess specifying in the given example
> > > > > > > which type of service I want might help, but in the meantime the
> > > > > > > example is leading straight to an error, which is confusing for
> > > > > > > newcomers.
>
> > > > > > > Cheers,
>
> > > > > > > Yannick
>
> > > > > winmail.dat
> > > > > 5KDownload

I'm sure I have those images somewhere but I've go a new laptop
recently so I'll have to drag them off the backup. Bear with me.

Simon
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "phpsoa" group.
To post to this group, send email to phpsoa@...
To unsubscribe from this group, send email to phpsoa+unsubscribe@...
For more options, visit this group at http://groups.google.co.uk/group/phpsoa?hl=en
-~----------~----~----~----~------~----~------~--~---

Re: Impact of SCA on performance?

2008-07-30T02:33:06Z

On 28 Jul, 01:55, Yannick <ywarn...@...> wrote:

> Hi again,
>
> If I decide to use SCA to provide services from my existing classes,
> should I be worried about performances in terms of parsing? Will any
> single include of this class file trigger a parsing of my PHPDoc
> documentation, or is it going to detect, somehow, that the class has
> been called through a local call rather than a web service, and
> consequently ignore the parsing?
>
> Thanks,
>
> Yannick

Hi Yannick

Apols for not being very responsive here. I have of late been spending
most of my time on the Java SCA implementation over in Apache and over
there we are in the middle of trying to get a release out (with all
the fun and games that involves). I won't be able to spend much time
on PHP SCA code changes in the near future but I'll try and stay on
the list and help if I can.

If I remember correctly there is code to detect if the class file
(that represents an SCA component) is being included by a wrapper
script or if it is being called by PHP directly in response to a user
request. The idea behind this is that you may not want to always use
the classes as SCA components and hence don't want to incur the
overhead of the parsing. In the case that you do want to have a class
included in a wrapper file but also act as a service component we
included a "dispatch" method that allowed the ongoing request to be
delegated to some included SCA component. In which case the parsing
will be done. Someone on the list a long time ago wanted to set up his
web server with a stucture something like...

htdocs/
mywrapperscript.php
privatedocs/
myscacomponent.php

and have mywrapperscript.php delgate to myscacomponent.php. This was
the motivation behind the "dispatch" method.

I also have a vague recollection that there is some optimization in
the bindings to detect if the target is a local component but I may
just be imagining it. I'll have to go check.

Regards

Simon
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "phpsoa" group.
To post to this group, send email to phpsoa@...
To unsubscribe from this group, send email to phpsoa+unsubscribe@...
For more options, visit this group at http://groups.google.co.uk/group/phpsoa?hl=en
-~----------~----~----~----~------~----~------~--~---

Re: PHPDoc parsing too restrictive?

2008-07-30T01:29:34Z

Hi Yannick,

The CLA is a Contributors License Agreement. The one we have in place
for SCA_SDO is derived from the CLA which covers contributions to the
Apache projects. It's contained in the SCA_SDO distribution and is a
text document called "CLA". We are only able to include contributions
to the project from people who have signed the CLA.

Regards, Graham.

On 30 Jul, 04:10, Yannick <ywarn...@...> wrote:

> What's the CLA?
>
> On 29 juil, 05:07, Matthew Peters <matthew.f.pet...@...>
> wrote:
>
> > Hi Yannick, that's really bad! You could spend hours hunting that down
> > and then you would really hate SCA at the end of it. I don't know what
> > causes that but I totally agree that it should be fixed. One of the
> > package owners will get to it in due course, or of course anyone is
> > free to sign the CLA and submit a patch.
>
> > Matthew
>
> > On Jul 28, 2:52 am, Yannick <ywarn...@...> wrote:
>
> > > Hi again,
>
> > > Apparently, the parsing of the PHPDoc comments is so severe that if I
> > > use:
>
> > > /**
> > > * This library provides functions for user management.
> > > * it in your code to use its functionality.
> > > *
> > > * @service
> > > * @binding.soap
> > > *
> > > */
>
> > > it won't work, but if I add one space before the star on the line
> > > before the last, then it works:
>
> > > /**
> > > * This library provides functions for user management.
> > > * it in your code to use its functionality.
> > > *
> > > * @service
> > > * @binding.soap
> > > *
> > > */
>
> > > However, the last line (the closing tag) works, with or without space.
> > > I haven't found any documentation about this, but it sure takes some
> > > time to figure out! (and error reporting is un-existing about that
> > > one)
>
> > > Isn't this a little too restrictive for a package that is supposed to
> > > provide a simple mechanism of re-use of existing functions?
>
> > > Yannick

Re: Possible to offer a service from a simple function?

2008-07-29T20:25:06Z

Or actually I might use SCA, but will newly built methods, which kinds
of defeats half the purpose.

On 29 juil, 22:22, Yannick <ywarn...@...> wrote:

> I'd really like to get started soon on web services implementation,
> and the series of e-mails I have sent give a clear idea of my concerns
> regarding SCA. I won't lie, I'm currently looking at other projects
> because of the shortcomings I have found in SCA, which kind of sucks
> as I really liked the idea behind SCA (re-use of existing functions
> using PHPDoc comments). On the other hand, I really can't see how one
> could provide web services using existing functions if:
>
> - they absolutely have to use classes
> - the files must have the same name as the class inside (What if there
> are two classes inside? What if you have an existing open-source
> project with lots of files depending on your class?). Apparently there
> is no way either to include a class-definition file intp a placeholder
> file which holds the right filename (because of the time at which the
> inclusion statement is processed the comments are already gone).
> - there is no security check anywhere
> - a missing space or a minor difference in the PHPDoc format can break
> the parsing process
>
> Anyway, if it doesn't work out now, it might work out later. I'll try
> to assist in fixing all these little issues that make it very
> difficult to use for me (and in the meantime, I'll probably fall down
> to a PHP solution like NuSOAP or something of the likes).
>
> Thanks anyway,
>
> Yannick
>
> On 27 juil, 19:52, Yannick <ywarn...@...> wrote:
>
> > Hi there,
>
> > As I am trying out SCA, a bunch of questions come to mind. I'll try to
> > stick to one-question-per-mail for clarity and indexing of the
> > answers.
>
> > Following the documentation herehttp://www.osoa.org/display/PHP/SCA+Documentation#SCADocumentation-2:
> > "...PHP annotations are used to define PHP classes as SCA
> > components,...".
> > As far as I can see, there's no way to use a simple functions library
> > and provide web services from it, is there?
>
> > If not, considering a functions library should also use a file-level
> > header for PHPDocumentor, is there a particular reason why it is not
> > possible to use simple functions?
>
> > Thanks,
>
> > Yannick

Re: Possible to offer a service from a simple function?

2008-07-29T20:22:34Z

I'd really like to get started soon on web services implementation,
and the series of e-mails I have sent give a clear idea of my concerns
regarding SCA. I won't lie, I'm currently looking at other projects
because of the shortcomings I have found in SCA, which kind of sucks
as I really liked the idea behind SCA (re-use of existing functions
using PHPDoc comments). On the other hand, I really can't see how one
could provide web services using existing functions if:

- they absolutely have to use classes
- the files must have the same name as the class inside (What if there
are two classes inside? What if you have an existing open-source
project with lots of files depending on your class?). Apparently there
is no way either to include a class-definition file intp a placeholder
file which holds the right filename (because of the time at which the
inclusion statement is processed the comments are already gone).
- there is no security check anywhere
- a missing space or a minor difference in the PHPDoc format can break
the parsing process

Anyway, if it doesn't work out now, it might work out later. I'll try
to assist in fixing all these little issues that make it very
difficult to use for me (and in the meantime, I'll probably fall down
to a PHP solution like NuSOAP or something of the likes).

Thanks anyway,

Yannick

On 27 juil, 19:52, Yannick <ywarn...@...> wrote:

> Hi there,
>
> As I am trying out SCA, a bunch of questions come to mind. I'll try to
> stick to one-question-per-mail for clarity and indexing of the
> answers.
>
> Following the documentation herehttp://www.osoa.org/display/PHP/SCA+Documentation#SCADocumentation-2:
> "...PHP annotations are used to define PHP classes as SCA
> components,...".
> As far as I can see, there's no way to use a simple functions library
> and provide web services from it, is there?
>
> If not, considering a functions library should also use a file-level
> header for PHPDocumentor, is there a particular reason why it is not
> possible to use simple functions?
>
> Thanks,
>
> Yannick

Re: SCA services access control...?

2008-07-29T20:15:20Z

Anybody got anything to say about this?

On 27 juil, 20:11, Yannick <ywarn...@...> wrote:

> Hi,
>
> I think I mentioned it the first time I sent an e-mail on this list,
> but one of the major problems I have with using SCA is that, if I do
> implement it into existing classes, I don't want just anyone to be
> able to use them freely.
>
> In Dokeos (and outside of any web services context), we rely on an
> initial authentication process (using sessions) to make sure the user
> is authorized to do what he is trying to do.
>
> However, if I want to take the full benefit out of SCA, I would like
> to be able to re-use my existing functions and *just* add a few
> comments here and there, and be done with it. Now the problem is that,
> if I do that, I inevitably loose the "session" context (as I am going
> through web services), and so I loose the authentication pre-check.
>
> This is a big problem to me, as adding an authentication process
> specifically for the web services, it means I *have to* reimplement
> most of my functions to add an authentication layer.
>
> I remember Caroline saying that someone was remotely working on/
> thinking about the topic, but haven't seen any discussion about it
> since then.
>
> How are other people here dealing with that?
> This is most likely to be the dead-end for us in terms of either
> adopting SCA_SDO or at least considering it as a real benefit.
>
> From the top of my head, I would say that if there was a way to
> configure a web service transparently to work in an "authenticated
> mode" and that, from there on, it always added a required "first"
> parameter being a shared key, and optionally identified the source by
> IP address, it would be enough.
>
> Something like adding a parameter @security.shared_key ../mykey.php in
> the class documentation, that would automatically:
> - generate a modified WSDL that shows a shared_key param as a first
> parameter for any function
> - add a check of this first parameter before going through with the
> answer to the service request
>
> What would be the likeliness of that idea to be integrated into
> SCA_SDO? We have plans for a release of our next Dokeos version at the
> end of September. If it is likely, then how likely would it be that a
> modified version of SCA_SDO can be rolled into PECL by then (because,
> of course, we want our users to be able to use the feature without
> having to pack SCA_SDO in our package)? As SCA_SDO is not written in
> PHP, it would be difficult to me to contribute code, but I can
> certainly contribute ideas, analysis and testing.
>
> Yannick

Re: Error with documentation example

2008-07-29T20:11:57Z

Thanks

On 29 juil, 08:17, Graham Charters <gchart...@...> wrote:

> Hi Matthew,
>
> Thanks for making these changes. I was going to, but got derailed by
> the fact that the first ones are in images. I see these haven't been
> changed. I think Simon Laws created these and I don't have the
> originals. If we can't get the originals we'll need to recreate them,
> or remove the images.
>
> Regards, Graham.
>
> On 29 Jul, 11:03, Matthew Peters <matthew.f.pet...@...>
> wrote:
>
> > I just went through the page and changed all the binding.ws (and a
> > couple of binding.wsdl) to binding.soap.
>
> > I also sprinkled a warning that the most up to date documentation is
> > on php.net through the document:
>
> > || _The most up to date documentation is to be found on the php.net
> > site, at [http://www.php.net/manual/en/book.sca.php] for example_ ||
>
> > Matthew
>
> > On Jul 29, 8:21 am, Graham Charters <gchart...@...> wrote:
>
> > > Hi Yannick,
>
> > > Thanks for pointing out the documentation problem on osoa.org. I'll
> > > try to fix that shortly.
>
> > > Dalibor is correct that WSDL is only generated for binding.soap.
> > > Other bindings will generate their own kinds of service descriptions
> > > where appropriate. For example, binding.jsonrpc with generate a
> > > service method description if you add ?smd.
>
> > > Regards, Graham.
>
> > > On 28 Jul, 00:01, Dalibor Andzakovic <Dalibor.Andzako...@...>
> > > wrote:
>
> > > > Correct. WSDL only gets created for SOAP services AFAIK.
>
> > > > dali
>
> > > > -----Original Message-----
> > > > From: phpsoa@... on behalf of Yannick
> > > > Sent: Mon 2008-07-28 11:00
> > > > To: phpsoa
> > > > Subject: [phpsoa] Re: Error with documentation example
>
> > > > Sorry, @binding.soap definitely works. I've been trying all the other
> > > > types (atom, jsonrpc, message, restrpc, tuscany, ebaysoap, local,
> > > > restresource, xmlrpc) but none of these generate a wsdl, even though
> > > > they don't generate any error message either.
> > > > Is that due to something proper to each of these other web services
> > > > types?
>
> > > > Yannick
>
> > > > On 27 juil, 17:39, Yannick <ywarn...@...> wrote:
> > > > > Like I said, finding the problem was not difficult nor long, but it's
> > > > > still confusing that there is no explanation of what "ws" could be
> > > > > replaced by in @binding.ws. Of course, replacing it by @binding.soap
> > > > > worked immediately.
> > > > > However, I tried to change it to @binding.restrpc and that,
> > > > > apparently, brings me back to the initial state (blank page); but this
> > > > > time I get no error report.
> > > > > Changing it back to @binding.soap doesn't work.
>
> > > > > Yannick
>
> > > > > On 26 juil, 18:24, Yannick <ywarn...@...> wrote:
>
> > > > > > Hi there,
>
> > > > > > I'm currently taking my first steps with SCA-SDO following the example
> > > > > > given here:
>
> > > > > >http://www.osoa.org/display/PHP/SCA+Documentation#SCADocumentation-2.5
>
> > > > > > I am using an Ubuntu 8.04 system ad I downloaded SCA_SDO using the
> > > > > > PECL command line interface.
> > > > > > Now I'm sure I'm going to find the problem soon, but as the
> > > > > > documentation, as it is, is leading me to a problem and obviously I
> > > > > > can't create and account to edit that page, I wanted to mention it.
>
> > > > > > When I try getting the WSDL for that page, I get a (double) error
> > > > > > message:
>
> > > > > > [Sat Jul 26 11:58:27 2008] [error] [client 127.0.0.1] PHP Warning:
> > > > > > SCA_Binding_Factory::require(SCA/Bindings/ws/RequestTester.php) [<a
> > > > > > href='function.SCA-Binding-Factory-require'>function.SCA-Binding-
> > > > > > Factory-require</a>]: failed to open stream: No such file or directory
> > > > > > in /usr/share/php/SCA/SCA_BindingFactory.php on line 68
> > > > > > [Sat Jul 26 11:58:27 2008] [error] [client 127.0.0.1] PHP Fatal
> > > > > > error: SCA_Binding_Factory::require() [<a
> > > > > > href='function.require'>function.require</a>]: Failed opening required
> > > > > > 'SCA/Bindings/ws/RequestTester.php' (include_path='.:/usr/share/php:/
> > > > > > usr/share/pear') in /usr/share/php/SCA/SCA_BindingFactory.php on line
> > > > > > 68
>
> > > > > > Looking into my /usr/share/php/SCA/ directory, I have:
>
> > > > > > /usr/share/php/SCA/Bindings$ ls
> > > > > > atom jsonrpc message restrpc tuscany
> > > > > > ebaysoap local restresource soap xmlrpc
>
> > > > > > So, no directory called "ws/". I guess specifying in the given example
> > > > > > which type of service I want might help, but in the meantime the
> > > > > > example is leading straight to an error, which is confusing for
> > > > > > newcomers.
>
> > > > > > Cheers,
>
> > > > > > Yannick
>
> > > > winmail.dat
> > > > 5KDownload

Re: PHPDoc parsing too restrictive?

2008-07-29T20:10:21Z

What's the CLA?

On 29 juil, 05:07, Matthew Peters <matthew.f.pet...@...>
wrote:

> Hi Yannick, that's really bad! You could spend hours hunting that down
> and then you would really hate SCA at the end of it. I don't know what
> causes that but I totally agree that it should be fixed. One of the
> package owners will get to it in due course, or of course anyone is
> free to sign the CLA and submit a patch.
>
> Matthew
>
> On Jul 28, 2:52 am, Yannick <ywarn...@...> wrote:
>
> > Hi again,
>
> > Apparently, the parsing of the PHPDoc comments is so severe that if I
> > use:
>
> > /**
> > * This library provides functions for user management.
> > * it in your code to use its functionality.
> > *
> > * @service
> > * @binding.soap
> > *
> > */
>
> > it won't work, but if I add one space before the star on the line
> > before the last, then it works:
>
> > /**
> > * This library provides functions for user management.
> > * it in your code to use its functionality.
> > *
> > * @service
> > * @binding.soap
> > *
> > */
>
> > However, the last line (the closing tag) works, with or without space.
> > I haven't found any documentation about this, but it sure takes some
> > time to figure out! (and error reporting is un-existing about that
> > one)
>
> > Isn't this a little too restrictive for a package that is supposed to
> > provide a simple mechanism of re-use of existing functions?
>
> > Yannick

Re: Error with documentation example

2008-07-29T06:17:41Z

Hi Matthew,

Thanks for making these changes. I was going to, but got derailed by
the fact that the first ones are in images. I see these haven't been
changed. I think Simon Laws created these and I don't have the
originals. If we can't get the originals we'll need to recreate them,
or remove the images.

Regards, Graham.

On 29 Jul, 11:03, Matthew Peters <matthew.f.pet...@...>
wrote:

> I just went through the page and changed all the binding.ws (and a
> couple of binding.wsdl) to binding.soap.
>
> I also sprinkled a warning that the most up to date documentation is
> on php.net through the document:
>
> || _The most up to date documentation is to be found on the php.net
> site, at [http://www.php.net/manual/en/book.sca.php] for example_ ||
>
> Matthew
>
> On Jul 29, 8:21 am, Graham Charters <gchart...@...> wrote:
>
> > Hi Yannick,
>
> > Thanks for pointing out the documentation problem on osoa.org. I'll
> > try to fix that shortly.
>
> > Dalibor is correct that WSDL is only generated for binding.soap.
> > Other bindings will generate their own kinds of service descriptions
> > where appropriate. For example, binding.jsonrpc with generate a
> > service method description if you add ?smd.
>
> > Regards, Graham.
>
> > On 28 Jul, 00:01, Dalibor Andzakovic <Dalibor.Andzako...@...>
> > wrote:
>
> > > Correct. WSDL only gets created for SOAP services AFAIK.
>
> > > dali
>
> > > -----Original Message-----
> > > From: phpsoa@... on behalf of Yannick
> > > Sent: Mon 2008-07-28 11:00
> > > To: phpsoa
> > > Subject: [phpsoa] Re: Error with documentation example
>
> > > Sorry, @binding.soap definitely works. I've been trying all the other
> > > types (atom, jsonrpc, message, restrpc, tuscany, ebaysoap, local,
> > > restresource, xmlrpc) but none of these generate a wsdl, even though
> > > they don't generate any error message either.
> > > Is that due to something proper to each of these other web services
> > > types?
>
> > > Yannick
>
> > > On 27 juil, 17:39, Yannick <ywarn...@...> wrote:
> > > > Like I said, finding the problem was not difficult nor long, but it's
> > > > still confusing that there is no explanation of what "ws" could be
> > > > replaced by in @binding.ws. Of course, replacing it by @binding.soap
> > > > worked immediately.
> > > > However, I tried to change it to @binding.restrpc and that,
> > > > apparently, brings me back to the initial state (blank page); but this
> > > > time I get no error report.
> > > > Changing it back to @binding.soap doesn't work.
>
> > > > Yannick
>
> > > > On 26 juil, 18:24, Yannick <ywarn...@...> wrote:
>
> > > > > Hi there,
>
> > > > > I'm currently taking my first steps with SCA-SDO following the example
> > > > > given here:
>
> > > > >http://www.osoa.org/display/PHP/SCA+Documentation#SCADocumentation-2.5
>
> > > > > I am using an Ubuntu 8.04 system ad I downloaded SCA_SDO using the
> > > > > PECL command line interface.
> > > > > Now I'm sure I'm going to find the problem soon, but as the
> > > > > documentation, as it is, is leading me to a problem and obviously I
> > > > > can't create and account to edit that page, I wanted to mention it.
>
> > > > > When I try getting the WSDL for that page, I get a (double) error
> > > > > message:
>
> > > > > [Sat Jul 26 11:58:27 2008] [error] [client 127.0.0.1] PHP Warning:
> > > > > SCA_Binding_Factory::require(SCA/Bindings/ws/RequestTester.php) [<a
> > > > > href='function.SCA-Binding-Factory-require'>function.SCA-Binding-
> > > > > Factory-require</a>]: failed to open stream: No such file or directory
> > > > > in /usr/share/php/SCA/SCA_BindingFactory.php on line 68
> > > > > [Sat Jul 26 11:58:27 2008] [error] [client 127.0.0.1] PHP Fatal
> > > > > error: SCA_Binding_Factory::require() [<a
> > > > > href='function.require'>function.require</a>]: Failed opening required
> > > > > 'SCA/Bindings/ws/RequestTester.php' (include_path='.:/usr/share/php:/
> > > > > usr/share/pear') in /usr/share/php/SCA/SCA_BindingFactory.php on line
> > > > > 68
>
> > > > > Looking into my /usr/share/php/SCA/ directory, I have:
>
> > > > > /usr/share/php/SCA/Bindings$ ls
> > > > > atom jsonrpc message restrpc tuscany
> > > > > ebaysoap local restresource soap xmlrpc
>
> > > > > So, no directory called "ws/". I guess specifying in the given example
> > > > > which type of service I want might help, but in the meantime the
> > > > > example is leading straight to an error, which is confusing for
> > > > > newcomers.
>
> > > > > Cheers,
>
> > > > > Yannick
>
> > > winmail.dat
> > > 5KDownload

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "phpsoa" group.
To post to this group, send email to phpsoa@...
To unsubscribe from this group, send email to phpsoa-unsubscribe@...
For more options, visit this group at http://groups.google.co.uk/group/phpsoa?hl=en
-~----------~----~----~----~------~----~------~--~---

Re: PHPDoc parsing too restrictive?

2008-07-29T03:07:47Z

Hi Yannick, that's really bad! You could spend hours hunting that down
and then you would really hate SCA at the end of it. I don't know what
causes that but I totally agree that it should be fixed. One of the
package owners will get to it in due course, or of course anyone is
free to sign the CLA and submit a patch.

Matthew

On Jul 28, 2:52 am, Yannick <ywarn...@...> wrote:

> Hi again,
>
> Apparently, the parsing of the PHPDoc comments is so severe that if I
> use:
>
> /**
> * This library provides functions for user management.
> * it in your code to use its functionality.
> *
> * @service
> * @binding.soap
> *
> */
>
> it won't work, but if I add one space before the star on the line
> before the last, then it works:
>
> /**
> * This library provides functions for user management.
> * it in your code to use its functionality.
> *
> * @service
> * @binding.soap
> *
> */
>
> However, the last line (the closing tag) works, with or without space.
> I haven't found any documentation about this, but it sure takes some
> time to figure out! (and error reporting is un-existing about that
> one)
>
> Isn't this a little too restrictive for a package that is supposed to
> provide a simple mechanism of re-use of existing functions?
>
> Yannick

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "phpsoa" group.
To post to this group, send email to phpsoa@...
To unsubscribe from this group, send email to phpsoa-unsubscribe@...
For more options, visit this group at http://groups.google.co.uk/group/phpsoa?hl=en
-~----------~----~----~----~------~----~------~--~---

Re: Error with documentation example

2008-07-29T03:03:36Z

I just went through the page and changed all the binding.ws (and a
couple of binding.wsdl) to binding.soap.

I also sprinkled a warning that the most up to date documentation is
on php.net through the document:

|| _The most up to date documentation is to be found on the php.net
site, at [http://www.php.net/manual/en/book.sca.php] for example_ ||

Matthew

On Jul 29, 8:21 am, Graham Charters <gchart...@...> wrote:

> Hi Yannick,
>
> Thanks for pointing out the documentation problem on osoa.org. I'll
> try to fix that shortly.
>
> Dalibor is correct that WSDL is only generated for binding.soap.
> Other bindings will generate their own kinds of service descriptions
> where appropriate. For example, binding.jsonrpc with generate a
> service method description if you add ?smd.
>
> Regards, Graham.
>
> On 28 Jul, 00:01, Dalibor Andzakovic <Dalibor.Andzako...@...>
> wrote:
>
> > Correct. WSDL only gets created for SOAP services AFAIK.
>
> > dali
>
> > -----Original Message-----
> > From: phpsoa@... on behalf of Yannick
> > Sent: Mon 2008-07-28 11:00
> > To: phpsoa
> > Subject: [phpsoa] Re: Error with documentation example
>
> > Sorry, @binding.soap definitely works. I've been trying all the other
> > types (atom, jsonrpc, message, restrpc, tuscany, ebaysoap, local,
> > restresource, xmlrpc) but none of these generate a wsdl, even though
> > they don't generate any error message either.
> > Is that due to something proper to each of these other web services
> > types?
>
> > Yannick
>
> > On 27 juil, 17:39, Yannick <ywarn...@...> wrote:
> > > Like I said, finding the problem was not difficult nor long, but it's
> > > still confusing that there is no explanation of what "ws" could be
> > > replaced by in @binding.ws. Of course, replacing it by @binding.soap
> > > worked immediately.
> > > However, I tried to change it to @binding.restrpc and that,
> > > apparently, brings me back to the initial state (blank page); but this
> > > time I get no error report.
> > > Changing it back to @binding.soap doesn't work.
>
> > > Yannick
>
> > > On 26 juil, 18:24, Yannick <ywarn...@...> wrote:
>
> > > > Hi there,
>
> > > > I'm currently taking my first steps with SCA-SDO following the example
> > > > given here:
>
> > > >http://www.osoa.org/display/PHP/SCA+Documentation#SCADocumentation-2.5
>
> > > > I am using an Ubuntu 8.04 system ad I downloaded SCA_SDO using the
> > > > PECL command line interface.
> > > > Now I'm sure I'm going to find the problem soon, but as the
> > > > documentation, as it is, is leading me to a problem and obviously I
> > > > can't create and account to edit that page, I wanted to mention it.
>
> > > > When I try getting the WSDL for that page, I get a (double) error
> > > > message:
>
> > > > [Sat Jul 26 11:58:27 2008] [error] [client 127.0.0.1] PHP Warning:
> > > > SCA_Binding_Factory::require(SCA/Bindings/ws/RequestTester.php) [<a
> > > > href='function.SCA-Binding-Factory-require'>function.SCA-Binding-
> > > > Factory-require</a>]: failed to open stream: No such file or directory
> > > > in /usr/share/php/SCA/SCA_BindingFactory.php on line 68
> > > > [Sat Jul 26 11:58:27 2008] [error] [client 127.0.0.1] PHP Fatal
> > > > error: SCA_Binding_Factory::require() [<a
> > > > href='function.require'>function.require</a>]: Failed opening required
> > > > 'SCA/Bindings/ws/RequestTester.php' (include_path='.:/usr/share/php:/
> > > > usr/share/pear') in /usr/share/php/SCA/SCA_BindingFactory.php on line
> > > > 68
>
> > > > Looking into my /usr/share/php/SCA/ directory, I have:
>
> > > > /usr/share/php/SCA/Bindings$ ls
> > > > atom jsonrpc message restrpc tuscany
> > > > ebaysoap local restresource soap xmlrpc
>
> > > > So, no directory called "ws/". I guess specifying in the given example
> > > > which type of service I want might help, but in the meantime the
> > > > example is leading straight to an error, which is confusing for
> > > > newcomers.
>
> > > > Cheers,
>
> > > > Yannick
>
> > winmail.dat
> > 5KDownload

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "phpsoa" group.
To post to this group, send email to phpsoa@...
To unsubscribe from this group, send email to phpsoa-unsubscribe@...
For more options, visit this group at http://groups.google.co.uk/group/phpsoa?hl=en
-~----------~----~----~----~------~----~------~--~---

Re: Error with documentation example

2008-07-29T00:21:49Z

Hi Yannick,

Thanks for pointing out the documentation problem on osoa.org. I'll
try to fix that shortly.

Dalibor is correct that WSDL is only generated for binding.soap.
Other bindings will generate their own kinds of service descriptions
where appropriate. For example, binding.jsonrpc with generate a
service method description if you add ?smd.

Regards, Graham.

On 28 Jul, 00:01, Dalibor Andzakovic <Dalibor.Andzako...@...>
wrote:

> Correct. WSDL only gets created for SOAP services AFAIK.
>
> dali
>
> -----Original Message-----
> From: phpsoa@... on behalf of Yannick
> Sent: Mon 2008-07-28 11:00
> To: phpsoa
> Subject: [phpsoa] Re: Error with documentation example
>
> Sorry, @binding.soap definitely works. I've been trying all the other
> types (atom, jsonrpc, message, restrpc, tuscany, ebaysoap, local,
> restresource, xmlrpc) but none of these generate a wsdl, even though
> they don't generate any error message either.
> Is that due to something proper to each of these other web services
> types?
>
> Yannick
>
> On 27 juil, 17:39, Yannick <ywarn...@...> wrote:
> > Like I said, finding the problem was not difficult nor long, but it's
> > still confusing that there is no explanation of what "ws" could be
> > replaced by in @binding.ws. Of course, replacing it by @binding.soap
> > worked immediately.
> > However, I tried to change it to @binding.restrpc and that,
> > apparently, brings me back to the initial state (blank page); but this
> > time I get no error report.
> > Changing it back to @binding.soap doesn't work.
>
> > Yannick
>
> > On 26 juil, 18:24, Yannick <ywarn...@...> wrote:
>
> > > Hi there,
>
> > > I'm currently taking my first steps with SCA-SDO following the example
> > > given here:
>
> > >http://www.osoa.org/display/PHP/SCA+Documentation#SCADocumentation-2.5
>
> > > I am using an Ubuntu 8.04 system ad I downloaded SCA_SDO using the
> > > PECL command line interface.
> > > Now I'm sure I'm going to find the problem soon, but as the
> > > documentation, as it is, is leading me to a problem and obviously I
> > > can't create and account to edit that page, I wanted to mention it.
>
> > > When I try getting the WSDL for that page, I get a (double) error
> > > message:
>
> > > [Sat Jul 26 11:58:27 2008] [error] [client 127.0.0.1] PHP Warning:
> > > SCA_Binding_Factory::require(SCA/Bindings/ws/RequestTester.php) [<a
> > > href='function.SCA-Binding-Factory-require'>function.SCA-Binding-
> > > Factory-require</a>]: failed to open stream: No such file or directory
> > > in /usr/share/php/SCA/SCA_BindingFactory.php on line 68
> > > [Sat Jul 26 11:58:27 2008] [error] [client 127.0.0.1] PHP Fatal
> > > error: SCA_Binding_Factory::require() [<a
> > > href='function.require'>function.require</a>]: Failed opening required
> > > 'SCA/Bindings/ws/RequestTester.php' (include_path='.:/usr/share/php:/
> > > usr/share/pear') in /usr/share/php/SCA/SCA_BindingFactory.php on line
> > > 68
>
> > > Looking into my /usr/share/php/SCA/ directory, I have:
>
> > > /usr/share/php/SCA/Bindings$ ls
> > > atom jsonrpc message restrpc tuscany
> > > ebaysoap local restresource soap xmlrpc
>
> > > So, no directory called "ws/". I guess specifying in the given example
> > > which type of service I want might help, but in the meantime the
> > > example is leading straight to an error, which is confusing for
> > > newcomers.
>
> > > Cheers,
>
> > > Yannick
>
>
>
> winmail.dat
> 5KDownload

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "phpsoa" group.
To post to this group, send email to phpsoa@...
To unsubscribe from this group, send email to phpsoa-unsubscribe@...
For more options, visit this group at http://groups.google.co.uk/group/phpsoa?hl=en
-~----------~----~----~----~------~----~------~--~---

PHPDoc parsing too restrictive?

2008-07-27T18:52:39Z

Hi again,

Apparently, the parsing of the PHPDoc comments is so severe that if I
use:

/**
* This library provides functions for user management.
* it in your code to use its functionality.
*
* @service
* @binding.soap
*
*/

it won't work, but if I add one space before the star on the line
before the last, then it works:

/**
* This library provides functions for user management.
* it in your code to use its functionality.
*
* @service
* @binding.soap
*
*/

However, the last line (the closing tag) works, with or without space.
I haven't found any documentation about this, but it sure takes some
time to figure out! (and error reporting is un-existing about that
one)

Isn't this a little too restrictive for a package that is supposed to
provide a simple mechanism of re-use of existing functions?

Yannick
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "phpsoa" group.
To post to this group, send email to phpsoa@...
To unsubscribe from this group, send email to phpsoa-unsubscribe@...
For more options, visit this group at http://groups.google.co.uk/group/phpsoa?hl=en
-~----------~----~----~----~------~----~------~--~---

SCA services access control...?

2008-07-27T18:11:23Z

Hi,

I think I mentioned it the first time I sent an e-mail on this list,
but one of the major problems I have with using SCA is that, if I do
implement it into existing classes, I don't want just anyone to be
able to use them freely.

In Dokeos (and outside of any web services context), we rely on an
initial authentication process (using sessions) to make sure the user
is authorized to do what he is trying to do.

However, if I want to take the full benefit out of SCA, I would like
to be able to re-use my existing functions and *just* add a few
comments here and there, and be done with it. Now the problem is that,
if I do that, I inevitably loose the "session" context (as I am going
through web services), and so I loose the authentication pre-check.

This is a big problem to me, as adding an authentication process
specifically for the web services, it means I *have to* reimplement
most of my functions to add an authentication layer.

I remember Caroline saying that someone was remotely working on/
thinking about the topic, but haven't seen any discussion about it
since then.

How are other people here dealing with that?
This is most likely to be the dead-end for us in terms of either
adopting SCA_SDO or at least considering it as a real benefit.

From the top of my head, I would say that if there was a way to
configure a web service transparently to work in an "authenticated
mode" and that, from there on, it always added a required "first"
parameter being a shared key, and optionally identified the source by
IP address, it would be enough.

Something like adding a parameter @security.shared_key ../mykey.php in
the class documentation, that would automatically:
- generate a modified WSDL that shows a shared_key param as a first
parameter for any function
- add a check of this first parameter before going through with the
answer to the service request

What would be the likeliness of that idea to be integrated into
SCA_SDO? We have plans for a release of our next Dokeos version at the
end of September. If it is likely, then how likely would it be that a
modified version of SCA_SDO can be rolled into PECL by then (because,
of course, we want our users to be able to use the feature without
having to pack SCA_SDO in our package)? As SCA_SDO is not written in
PHP, it would be difficult to me to contribute code, but I can
certainly contribute ideas, analysis and testing.

Yannick
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "phpsoa" group.
To post to this group, send email to phpsoa@...
To unsubscribe from this group, send email to phpsoa-unsubscribe@...
For more options, visit this group at http://groups.google.co.uk/group/phpsoa?hl=en
-~----------~----~----~----~------~----~------~--~---

Impact of SCA on performance?

2008-07-27T17:55:00Z

Hi again,

If I decide to use SCA to provide services from my existing classes,
should I be worried about performances in terms of parsing? Will any
single include of this class file trigger a parsing of my PHPDoc
documentation, or is it going to detect, somehow, that the class has
been called through a local call rather than a web service, and
consequently ignore the parsing?

Thanks,

Yannick
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "phpsoa" group.
To post to this group, send email to phpsoa@...
To unsubscribe from this group, send email to phpsoa-unsubscribe@...
For more options, visit this group at http://groups.google.co.uk/group/phpsoa?hl=en
-~----------~----~----~----~------~----~------~--~---

Possible to offer a service from a simple function?

2008-07-27T17:52:23Z

Hi there,

As I am trying out SCA, a bunch of questions come to mind. I'll try to
stick to one-question-per-mail for clarity and indexing of the
answers.

Following the documentation here http://www.osoa.org/display/PHP/SCA+Documentation#SCADocumentation-2:
"...PHP annotations are used to define PHP classes as SCA
components,...".
As far as I can see, there's no way to use a simple functions library
and provide web services from it, is there?

If not, considering a functions library should also use a file-level
header for PHPDocumentor, is there a particular reason why it is not
possible to use simple functions?

Thanks,

Yannick
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "phpsoa" group.
To post to this group, send email to phpsoa@...
To unsubscribe from this group, send email to phpsoa-unsubscribe@...
For more options, visit this group at http://groups.google.co.uk/group/phpsoa?hl=en
-~----------~----~----~----~------~----~------~--~---

Re: Error with documentation example

2008-07-27T16:01:39Z

Correct. WSDL only gets created for SOAP services AFAIK.

dali

-----Original Message-----
From: phpsoa@... on behalf of Yannick
Sent: Mon 2008-07-28 11:00
To: phpsoa
Subject: [phpsoa] Re: Error with documentation example

Sorry, @binding.soap definitely works. I've been trying all the other
types (atom, jsonrpc, message, restrpc, tuscany, ebaysoap, local,
restresource, xmlrpc) but none of these generate a wsdl, even though
they don't generate any error message either.
Is that due to something proper to each of these other web services
types?

Yannick

On 27 juil, 17:39, Yannick <ywarn...@...> wrote:

> Like I said, finding the problem was not difficult nor long, but it's
> still confusing that there is no explanation of what "ws" could be
> replaced by in @binding.ws. Of course, replacing it by @binding.soap
> worked immediately.
> However, I tried to change it to @binding.restrpc and that,
> apparently, brings me back to the initial state (blank page); but this
> time I get no error report.
> Changing it back to @binding.soap doesn't work.
>
> Yannick
>
> On 26 juil, 18:24, Yannick <ywarn...@...> wrote:
>
> > Hi there,
>
> > I'm currently taking my first steps with SCA-SDO following the example
> > given here:
>
> >http://www.osoa.org/display/PHP/SCA+Documentation#SCADocumentation-2.5
>
> > I am using an Ubuntu 8.04 system ad I downloaded SCA_SDO using the
> > PECL command line interface.
> > Now I'm sure I'm going to find the problem soon, but as the
> > documentation, as it is, is leading me to a problem and obviously I
> > can't create and account to edit that page, I wanted to mention it.
>
> > When I try getting the WSDL for that page, I get a (double) error
> > message:
>
> > [Sat Jul 26 11:58:27 2008] [error] [client 127.0.0.1] PHP Warning:
> > SCA_Binding_Factory::require(SCA/Bindings/ws/RequestTester.php) [<a
> > href='function.SCA-Binding-Factory-require'>function.SCA-Binding-
> > Factory-require</a>]: failed to open stream: No such file or directory
> > in /usr/share/php/SCA/SCA_BindingFactory.php on line 68
> > [Sat Jul 26 11:58:27 2008] [error] [client 127.0.0.1] PHP Fatal
> > error: SCA_Binding_Factory::require() [<a
> > href='function.require'>function.require</a>]: Failed opening required
> > 'SCA/Bindings/ws/RequestTester.php' (include_path='.:/usr/share/php:/
> > usr/share/pear') in /usr/share/php/SCA/SCA_BindingFactory.php on line
> > 68
>
> > Looking into my /usr/share/php/SCA/ directory, I have:
>
> > /usr/share/php/SCA/Bindings$ ls
> > atom jsonrpc message restrpc tuscany
> > ebaysoap local restresource soap xmlrpc
>
> > So, no directory called "ws/". I guess specifying in the given example
> > which type of service I want might help, but in the meantime the
> > example is leading straight to an error, which is confusing for
> > newcomers.
>
> > Cheers,
>
> > Yannick

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "phpsoa" group.
To post to this group, send email to phpsoa@...
To unsubscribe from this group, send email to phpsoa-unsubscribe@...
For more options, visit this group at http://groups.google.co.uk/group/phpsoa?hl=en
-~----------~----~----~----~------~----~------~--~---

winmail.dat (5K) Download Attachment