est,
Mike
> -Original Message-
> From: phpsoa@googlegroups.com [mailto:[EMAIL PROTECTED] On
> Behalf Of [EMAIL PROTECTED]
> Sent: May 7, 2007 6:15 AM
> To: phpsoa
> Subject: [phpsoa] Re: SCA Server Programming: Layout Issues
>
>
> Hi
>
> I just checked in a coupl
Hi
I just checked in a couple of changes to the new CURLEW branch. I've
been looking at the association between file name and service name in
the code and it's a bit intertwined at the moment. I'll start a new
thread on what this really means but in the mean time I've made the
following changes a
class names to files
easily.
Anyway, my $0.02.
Best,
Mike
> -Original Message-
> From: phpsoa@googlegroups.com [mailto:[EMAIL PROTECTED] On
> Behalf Of [EMAIL PROTECTED]
> Sent: May 4, 2007 9:53 AM
> To: phpsoa
> Subject: [phpsoa] Re: SCA Server Programming: Layout
Hi Mike
I had to do a presentation this morning so just got back to looking at
this. I started thinking about the API approach and thought I would
mock it up with what we have already before making changes. So
repeated the SCA initialization call that happens internally. I had a
HelloWorld test w
Hi Simon,
Thanks again for the reply. Comments follow:
> Ok, so let me just replay this to make sure I have understood. For 1
> and 3 you are looking to deploy like this:
>
> htdocs/
>MyPublic.php
> private/
>MyService.php
>
> Where MyPublic looks something like
>
>
> include 'boot
> 1) I have all my library files in a separate library directory. All
> libraries adhere to PEAR naming conventions, and directory placement
> 3) My public facing php files reference libraries behind what is
> publicly exposed via the web server
Ok, so let me just replay this to make sure I
