Re: SCA Server Programming: Layout Issues

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 as an experimrnt to see if the interface
works in
your environment...

SCA.php

Added a new operation SCA::dispatch(classname). This allows
the
incomming request to be dispatched to SCA as opposed to
calling the
SCA service locally from the php script, for example,

<?php
include 'Lib/HelloWorld.php';
SCA::dispatch('Lib_HelloWorld');
?>

The idea is it can take account of PEAR naming standards. To
achieve
this in this experiment I have made changes to

SCA_Helper.php

guessClassName() now goes on to look for matches using PEAR
coding
standards

getFileContainingClass() looks for included files based on
PEAR coding
standards. This is not a complete test at the moment

So you should be able to dispatch to your class file that
you are
including from outside of the htdocs directory. I haven't
tested with
the Zend Framwork methods you are using though so I'd be
interested to
hear what happens

The code in CURLEW is, currently, everything that Matthew
has just
released from head + these two changes.

Regards

Simon


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

Hi Simon,

Bang on.  Your mods did the trick.  My layout issues were
resolved.

I'm wondering, the default SCA bootstrap process (which is
based on
debug_backtrace), is that necessary, or somehow
override-able?  Ideally,
I'd like to avoid to calls two SCA::initComponent().

Best,

Mike



> -----Original Message-----
> From: phpsoagooglegroups.com [mailto:phpsoagooglegroups.com] On
> Behalf Of simonslawsgooglemail.com
> Sent: May 7, 2007 6:15 AM
> To: phpsoa
> Subject: [phpsoa] Re: SCA Server Programming: Layout
Issues
> 
> 
> 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 as an experimrnt to see if the
interface works in
> your environment...
> 
> SCA.php
> 
> Added a new operation SCA::dispatch(classname). This
allows the
> incomming request to be dispatched to SCA as opposed to
calling the
> SCA service locally from the php script, for example,
> 
> <?php
> include 'Lib/HelloWorld.php';
> SCA::dispatch('Lib_HelloWorld');
> ?>
> 
> The idea is it can take account of PEAR naming
standards. To achieve
> this in this experiment I have made changes to
> 
> SCA_Helper.php
> 
> guessClassName() now goes on to look for matches using
PEAR coding
> standards
> 
> getFileContainingClass() looks for included files based
on PEAR coding
> standards. This is not a complete test at the moment
> 
> So you should be able to dispatch to your class file
that you are
> including from outside of the htdocs directory. I
haven't tested with
> the Zend Framwork methods you are using though so I'd
be interested to
> hear what happens
> 
> The code in CURLEW is, currently, everything that
Matthew has just
> released from head + these two changes.
> 
> Regards
> 
> Simon
> 
> 
> E-mail messages may contain viruses, worms, or other
malicious code. By reading the message and opening any
attachments, the recipient accepts full responsibility for
taking protective action against such code. Henry Schein is
not liable for any loss or damage arising from this
message.

The information in this email is confidential and may be
legally privileged. It is intended solely for the
addressee(s). Access to this e-mail by anyone else is
unauthorized.

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