You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@flex.apache.org by "irwan.husein" <ir...@gmail.com> on 2014/10/27 07:56:45 UTC
Flex AMFPHP 2.2.1
Hi All,
i'm flex + php developer since flex 4.6
today i'm start migrating old amfphp server (1.9) to amfphp 2.2.1 + flex
4.13
unfortunately, i've found some problems
in amfphp 1.9, i can do remote call like this
*Flex Client :*
public var gateway:NetConnection;
var PHPParam:Object = new Object;
PHPParam.Parameter00 = 'param1';
PHPParam.Parameter01 = 'param2';
PHPParam.Parameter02 = 'param3';
gateway.call("someservice.somefunction", new Responder(resultData,
null),PHPParam);
*AMFPHP Services*
function somefunction($PHPParam)
{
$Param1 = $PHPParam['Parameter00'];
$Param2 = $PHPParam['Parameter01'];
$Param3 = $PHPParam['Parameter02'];
//do something
return "something";
}
but, in AMFPHP 2.2.1, i can't do it anymore, i can't sent object to php
services, only simple parameter.
in their website, they suggest using JSON statement, but theres no example
if anyone has ever experienced ?
or we just go with ValueObject approach?
regards,
Irwan
--
View this message in context: http://apache-flex-users.2333346.n4.nabble.com/Flex-AMFPHP-2-2-1-tp8506.html
Sent from the Apache Flex Users mailing list archive at Nabble.com.
Re: Flex AMFPHP 2.2.1
Posted by Justin Ransom Dallas <ju...@gmail.com>.
I use ZendAMF at work. It's not terribly difficult to get set up and
started.
On Mon, Oct 27, 2014 at 7:14 PM, irwan.husein <ir...@gmail.com>
wrote:
> yes, debugging in amfphp is headache sometimes.
> especially when integrating with another system like SAP RFC
>
> On 27 October 2014 17:20, Marcus Fritze [via Apache Flex Users] <
> ml-node+s2333346n8514h15@n4.nabble.com> wrote:
>
> > I never worked with ZendAMF, maybe someone else can say something about
> > pro and cons between ZendAMF and amfphp.
> >
> > Years ago, I think at this time, ZendAMF didn't even existed, so I
> started
> > with amfphp. But I am not sure.
> >
> > One disadvantage of amfphp is to debug not working requests. It's very
> > hard to find errors in complex requests.
> >
> > AND IMPORTANT: never send a object which has the same object (AS memory
> > reference) inside multiple times! this doesn't work!
> >
> > But overall amfphp works.
> >
> > Marcus
> >
> >
> > Am 27.10.2014 um 11:00 schrieb irwan.husein <[hidden email]
> > <http://user/SendEmail.jtp?type=node&node=8514&i=0>>:
> >
> > hi marcus,
> > it works... :D
> > just doing some find and replace, and all services OK again.
> >
> > btw, what's your opinion about ZendAMF and amfphp?
> > performance, deployment, etc..
> >
> > regards,
> >
> >
> > On 27 October 2014 16:35, Marcus Fritze [via Apache Flex Users] <
> > [hidden email] <http://user/SendEmail.jtp?type=node&node=8514&i=1>>
> wrote:
> >
> > Hi Irwan,
> >
> > I also experienced some changes when I switched from AMFPHP 1.9 to 2.0
> (or
> > later).
> >
> > My experience was that I had to change some of my PHP code. When I pass a
> > AS object, this is also a object in PHP and not a array
> >
> > maybe you should try:
> >
> > function somefunction($PHPParam)
> >
> > {
> >
> > $Param1 = $PHPParam->Parameter00;
> >
> > $Param2 = $PHPParam->Parameter01;
> >
> > $Param3 = $PHPParam->Parameter02;
> >
> >
> > //do something
> >
> > return "something";
> > }
> >
> > Best regards
> >
> > Marcus
> >
> > Am 27.10.2014 um 07:56 schrieb irwan.husein <[hidden email]
> > <http://user/SendEmail.jtp?type=node&node=8509&i=0>>:
> >
> >
> > Hi All,
> > i'm flex + php developer since flex 4.6
> > today i'm start migrating old amfphp server (1.9) to amfphp 2.2.1 + flex
> > 4.13
> >
> > unfortunately, i've found some problems
> > in amfphp 1.9, i can do remote call like this
> >
> > *Flex Client :*
> > public var gateway:NetConnection;
> >
> > var PHPParam:Object = new Object;
> > PHPParam.Parameter00 = 'param1';
> > PHPParam.Parameter01 = 'param2';
> > PHPParam.Parameter02 = 'param3';
> >
> > gateway.call("someservice.somefunction", new Responder(resultData,
> > null),PHPParam);
> >
> > *AMFPHP Services*
> >
> > function somefunction($PHPParam)
> > {
> > $Param1 = $PHPParam['Parameter00'];
> > $Param2 = $PHPParam['Parameter01'];
> > $Param3 = $PHPParam['Parameter02'];
> >
> > //do something
> > return "something";
> > }
> >
> > but, in AMFPHP 2.2.1, i can't do it anymore, i can't sent object to php
> > services, only simple parameter.
> > in their website, they suggest using JSON statement, but theres no
> example
> >
> > if anyone has ever experienced ?
> > or we just go with ValueObject approach?
> >
> > regards,
> > Irwan
> >
> >
> >
> > --
> > View this message in context:
> >
> >
> http://apache-flex-users.2333346.n4.nabble.com/Flex-AMFPHP-2-2-1-tp8506.html
> > Sent from the Apache Flex Users mailing list archive at Nabble.com.
> >
> >
> >
> > *signature.asc* (507 bytes) Download Attachment
> > <
> >
> http://apache-flex-users.2333346.n4.nabble.com/attachment/8509/0/signature.asc
> > >
> >
> >
> > ------------------------------
> > If you reply to this email, your message will be added to the discussion
> > below:
> >
> >
> >
> http://apache-flex-users.2333346.n4.nabble.com/Flex-AMFPHP-2-2-1-tp8506p8509.html
> > To unsubscribe from Flex AMFPHP 2.2.1, click here
> > <
> > href="
> http://apache-flex-users.2333346.n4.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml
> "
> > target="_top" rel="nofollow"
> > link="external">
> http://apache-flex-users.2333346.n4.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml
> > >
> >
> >
> >
> >
> >
> > --
> > View this message in context:
> >
> http://apache-flex-users.2333346.n4.nabble.com/Flex-AMFPHP-2-2-1-tp8506p8513.html
> > Sent from the Apache Flex Users mailing list archive at Nabble.com
> > <http://nabble.com/>.
> >
> >
> >
> > *signature.asc* (507 bytes) Download Attachment
> > <
> http://apache-flex-users.2333346.n4.nabble.com/attachment/8514/0/signature.asc
> >
> >
> >
> > ------------------------------
> > If you reply to this email, your message will be added to the discussion
> > below:
> >
> >
> http://apache-flex-users.2333346.n4.nabble.com/Flex-AMFPHP-2-2-1-tp8506p8514.html
> > To unsubscribe from Flex AMFPHP 2.2.1, click here
> > <
> http://apache-flex-users.2333346.n4.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=8506&code=aXJ3YW4uaHVzZWluQGdtYWlsLmNvbXw4NTA2fC0xMzI1NzY0NTI0
> >
> > .
> > NAML
> > <
> http://apache-flex-users.2333346.n4.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml
> >
> >
>
>
>
>
> --
> View this message in context:
> http://apache-flex-users.2333346.n4.nabble.com/Flex-AMFPHP-2-2-1-tp8506p8515.html
> Sent from the Apache Flex Users mailing list archive at Nabble.com.
>
--
Justin Dallas
Phone:814-880-5637
Re: Flex AMFPHP 2.2.1
Posted by "irwan.husein" <ir...@gmail.com>.
yes, debugging in amfphp is headache sometimes.
especially when integrating with another system like SAP RFC
On 27 October 2014 17:20, Marcus Fritze [via Apache Flex Users] <
ml-node+s2333346n8514h15@n4.nabble.com> wrote:
> I never worked with ZendAMF, maybe someone else can say something about
> pro and cons between ZendAMF and amfphp.
>
> Years ago, I think at this time, ZendAMF didn't even existed, so I started
> with amfphp. But I am not sure.
>
> One disadvantage of amfphp is to debug not working requests. It's very
> hard to find errors in complex requests.
>
> AND IMPORTANT: never send a object which has the same object (AS memory
> reference) inside multiple times! this doesn't work!
>
> But overall amfphp works.
>
> Marcus
>
>
> Am 27.10.2014 um 11:00 schrieb irwan.husein <[hidden email]
> <http://user/SendEmail.jtp?type=node&node=8514&i=0>>:
>
> hi marcus,
> it works... :D
> just doing some find and replace, and all services OK again.
>
> btw, what's your opinion about ZendAMF and amfphp?
> performance, deployment, etc..
>
> regards,
>
>
> On 27 October 2014 16:35, Marcus Fritze [via Apache Flex Users] <
> [hidden email] <http://user/SendEmail.jtp?type=node&node=8514&i=1>> wrote:
>
> Hi Irwan,
>
> I also experienced some changes when I switched from AMFPHP 1.9 to 2.0 (or
> later).
>
> My experience was that I had to change some of my PHP code. When I pass a
> AS object, this is also a object in PHP and not a array
>
> maybe you should try:
>
> function somefunction($PHPParam)
>
> {
>
> $Param1 = $PHPParam->Parameter00;
>
> $Param2 = $PHPParam->Parameter01;
>
> $Param3 = $PHPParam->Parameter02;
>
>
> //do something
>
> return "something";
> }
>
> Best regards
>
> Marcus
>
> Am 27.10.2014 um 07:56 schrieb irwan.husein <[hidden email]
> <http://user/SendEmail.jtp?type=node&node=8509&i=0>>:
>
>
> Hi All,
> i'm flex + php developer since flex 4.6
> today i'm start migrating old amfphp server (1.9) to amfphp 2.2.1 + flex
> 4.13
>
> unfortunately, i've found some problems
> in amfphp 1.9, i can do remote call like this
>
> *Flex Client :*
> public var gateway:NetConnection;
>
> var PHPParam:Object = new Object;
> PHPParam.Parameter00 = 'param1';
> PHPParam.Parameter01 = 'param2';
> PHPParam.Parameter02 = 'param3';
>
> gateway.call("someservice.somefunction", new Responder(resultData,
> null),PHPParam);
>
> *AMFPHP Services*
>
> function somefunction($PHPParam)
> {
> $Param1 = $PHPParam['Parameter00'];
> $Param2 = $PHPParam['Parameter01'];
> $Param3 = $PHPParam['Parameter02'];
>
> //do something
> return "something";
> }
>
> but, in AMFPHP 2.2.1, i can't do it anymore, i can't sent object to php
> services, only simple parameter.
> in their website, they suggest using JSON statement, but theres no example
>
> if anyone has ever experienced ?
> or we just go with ValueObject approach?
>
> regards,
> Irwan
>
>
>
> --
> View this message in context:
>
> http://apache-flex-users.2333346.n4.nabble.com/Flex-AMFPHP-2-2-1-tp8506.html
> Sent from the Apache Flex Users mailing list archive at Nabble.com.
>
>
>
> *signature.asc* (507 bytes) Download Attachment
> <
> http://apache-flex-users.2333346.n4.nabble.com/attachment/8509/0/signature.asc
> >
>
>
> ------------------------------
> If you reply to this email, your message will be added to the discussion
> below:
>
>
> http://apache-flex-users.2333346.n4.nabble.com/Flex-AMFPHP-2-2-1-tp8506p8509.html
> To unsubscribe from Flex AMFPHP 2.2.1, click here
> <
> href="http://apache-flex-users.2333346.n4.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml"
> target="_top" rel="nofollow"
> link="external">http://apache-flex-users.2333346.n4.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml
> >
>
>
>
>
>
> --
> View this message in context:
> http://apache-flex-users.2333346.n4.nabble.com/Flex-AMFPHP-2-2-1-tp8506p8513.html
> Sent from the Apache Flex Users mailing list archive at Nabble.com
> <http://nabble.com/>.
>
>
>
> *signature.asc* (507 bytes) Download Attachment
> <http://apache-flex-users.2333346.n4.nabble.com/attachment/8514/0/signature.asc>
>
>
> ------------------------------
> If you reply to this email, your message will be added to the discussion
> below:
>
> http://apache-flex-users.2333346.n4.nabble.com/Flex-AMFPHP-2-2-1-tp8506p8514.html
> To unsubscribe from Flex AMFPHP 2.2.1, click here
> <http://apache-flex-users.2333346.n4.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=8506&code=aXJ3YW4uaHVzZWluQGdtYWlsLmNvbXw4NTA2fC0xMzI1NzY0NTI0>
> .
> NAML
> <http://apache-flex-users.2333346.n4.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>
--
View this message in context: http://apache-flex-users.2333346.n4.nabble.com/Flex-AMFPHP-2-2-1-tp8506p8515.html
Sent from the Apache Flex Users mailing list archive at Nabble.com.
Re: Flex AMFPHP 2.2.1
Posted by Marcus Fritze <ma...@googlemail.com>.
I never worked with ZendAMF, maybe someone else can say something about pro and cons between ZendAMF and amfphp.
Years ago, I think at this time, ZendAMF didn't even existed, so I started with amfphp. But I am not sure.
One disadvantage of amfphp is to debug not working requests. It's very hard to find errors in complex requests.
AND IMPORTANT: never send a object which has the same object (AS memory reference) inside multiple times! this doesn't work!
But overall amfphp works.
Marcus
Am 27.10.2014 um 11:00 schrieb irwan.husein <ir...@gmail.com>:
> hi marcus,
> it works... :D
> just doing some find and replace, and all services OK again.
>
> btw, what's your opinion about ZendAMF and amfphp?
> performance, deployment, etc..
>
> regards,
>
>
> On 27 October 2014 16:35, Marcus Fritze [via Apache Flex Users] <
> ml-node+s2333346n8509h60@n4.nabble.com> wrote:
>
>> Hi Irwan,
>>
>> I also experienced some changes when I switched from AMFPHP 1.9 to 2.0 (or
>> later).
>>
>> My experience was that I had to change some of my PHP code. When I pass a
>> AS object, this is also a object in PHP and not a array
>>
>> maybe you should try:
>>
>> function somefunction($PHPParam)
>>
>> {
>>
>> $Param1 = $PHPParam->Parameter00;
>>
>> $Param2 = $PHPParam->Parameter01;
>>
>> $Param3 = $PHPParam->Parameter02;
>>
>>
>> //do something
>>
>> return "something";
>> }
>>
>> Best regards
>>
>> Marcus
>>
>> Am 27.10.2014 um 07:56 schrieb irwan.husein <[hidden email]
>> <http://user/SendEmail.jtp?type=node&node=8509&i=0>>:
>>
>> Hi All,
>> i'm flex + php developer since flex 4.6
>> today i'm start migrating old amfphp server (1.9) to amfphp 2.2.1 + flex
>> 4.13
>>
>> unfortunately, i've found some problems
>> in amfphp 1.9, i can do remote call like this
>>
>> *Flex Client :*
>> public var gateway:NetConnection;
>>
>> var PHPParam:Object = new Object;
>> PHPParam.Parameter00 = 'param1';
>> PHPParam.Parameter01 = 'param2';
>> PHPParam.Parameter02 = 'param3';
>>
>> gateway.call("someservice.somefunction", new Responder(resultData,
>> null),PHPParam);
>>
>> *AMFPHP Services*
>>
>> function somefunction($PHPParam)
>> {
>> $Param1 = $PHPParam['Parameter00'];
>> $Param2 = $PHPParam['Parameter01'];
>> $Param3 = $PHPParam['Parameter02'];
>>
>> //do something
>> return "something";
>> }
>>
>> but, in AMFPHP 2.2.1, i can't do it anymore, i can't sent object to php
>> services, only simple parameter.
>> in their website, they suggest using JSON statement, but theres no example
>>
>> if anyone has ever experienced ?
>> or we just go with ValueObject approach?
>>
>> regards,
>> Irwan
>>
>>
>>
>> --
>> View this message in context:
>> http://apache-flex-users.2333346.n4.nabble.com/Flex-AMFPHP-2-2-1-tp8506.html
>> Sent from the Apache Flex Users mailing list archive at Nabble.com.
>>
>>
>>
>> *signature.asc* (507 bytes) Download Attachment
>> <http://apache-flex-users.2333346.n4.nabble.com/attachment/8509/0/signature.asc>
>>
>>
>> ------------------------------
>> If you reply to this email, your message will be added to the discussion
>> below:
>>
>> http://apache-flex-users.2333346.n4.nabble.com/Flex-AMFPHP-2-2-1-tp8506p8509.html
>> To unsubscribe from Flex AMFPHP 2.2.1, click here
>> <http://apache-flex-users.2333346.n4.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=8506&code=aXJ3YW4uaHVzZWluQGdtYWlsLmNvbXw4NTA2fC0xMzI1NzY0NTI0>
>> .
>> NAML
>> <http://apache-flex-users.2333346.n4.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>>
>
>
>
>
> --
> View this message in context: http://apache-flex-users.2333346.n4.nabble.com/Flex-AMFPHP-2-2-1-tp8506p8513.html
> Sent from the Apache Flex Users mailing list archive at Nabble.com.
Re: Flex AMFPHP 2.2.1
Posted by "irwan.husein" <ir...@gmail.com>.
hi marcus,
it works... :D
just doing some find and replace, and all services OK again.
btw, what's your opinion about ZendAMF and amfphp?
performance, deployment, etc..
regards,
On 27 October 2014 16:35, Marcus Fritze [via Apache Flex Users] <
ml-node+s2333346n8509h60@n4.nabble.com> wrote:
> Hi Irwan,
>
> I also experienced some changes when I switched from AMFPHP 1.9 to 2.0 (or
> later).
>
> My experience was that I had to change some of my PHP code. When I pass a
> AS object, this is also a object in PHP and not a array
>
> maybe you should try:
>
> function somefunction($PHPParam)
>
> {
>
> $Param1 = $PHPParam->Parameter00;
>
> $Param2 = $PHPParam->Parameter01;
>
> $Param3 = $PHPParam->Parameter02;
>
>
> //do something
>
> return "something";
> }
>
> Best regards
>
> Marcus
>
> Am 27.10.2014 um 07:56 schrieb irwan.husein <[hidden email]
> <http://user/SendEmail.jtp?type=node&node=8509&i=0>>:
>
> Hi All,
> i'm flex + php developer since flex 4.6
> today i'm start migrating old amfphp server (1.9) to amfphp 2.2.1 + flex
> 4.13
>
> unfortunately, i've found some problems
> in amfphp 1.9, i can do remote call like this
>
> *Flex Client :*
> public var gateway:NetConnection;
>
> var PHPParam:Object = new Object;
> PHPParam.Parameter00 = 'param1';
> PHPParam.Parameter01 = 'param2';
> PHPParam.Parameter02 = 'param3';
>
> gateway.call("someservice.somefunction", new Responder(resultData,
> null),PHPParam);
>
> *AMFPHP Services*
>
> function somefunction($PHPParam)
> {
> $Param1 = $PHPParam['Parameter00'];
> $Param2 = $PHPParam['Parameter01'];
> $Param3 = $PHPParam['Parameter02'];
>
> //do something
> return "something";
> }
>
> but, in AMFPHP 2.2.1, i can't do it anymore, i can't sent object to php
> services, only simple parameter.
> in their website, they suggest using JSON statement, but theres no example
>
> if anyone has ever experienced ?
> or we just go with ValueObject approach?
>
> regards,
> Irwan
>
>
>
> --
> View this message in context:
> http://apache-flex-users.2333346.n4.nabble.com/Flex-AMFPHP-2-2-1-tp8506.html
> Sent from the Apache Flex Users mailing list archive at Nabble.com.
>
>
>
> *signature.asc* (507 bytes) Download Attachment
> <http://apache-flex-users.2333346.n4.nabble.com/attachment/8509/0/signature.asc>
>
>
> ------------------------------
> If you reply to this email, your message will be added to the discussion
> below:
>
> http://apache-flex-users.2333346.n4.nabble.com/Flex-AMFPHP-2-2-1-tp8506p8509.html
> To unsubscribe from Flex AMFPHP 2.2.1, click here
> <http://apache-flex-users.2333346.n4.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=8506&code=aXJ3YW4uaHVzZWluQGdtYWlsLmNvbXw4NTA2fC0xMzI1NzY0NTI0>
> .
> NAML
> <http://apache-flex-users.2333346.n4.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>
--
View this message in context: http://apache-flex-users.2333346.n4.nabble.com/Flex-AMFPHP-2-2-1-tp8506p8513.html
Sent from the Apache Flex Users mailing list archive at Nabble.com.
Re: Flex AMFPHP 2.2.1
Posted by Marcus Fritze <ma...@googlemail.com>.
Hi Irwan,
I also experienced some changes when I switched from AMFPHP 1.9 to 2.0 (or later).
My experience was that I had to change some of my PHP code. When I pass a AS object, this is also a object in PHP and not a array
maybe you should try:
function somefunction($PHPParam)
{
$Param1 = $PHPParam->Parameter00;
$Param2 = $PHPParam->Parameter01;
$Param3 = $PHPParam->Parameter02;
//do something
return "something";
}
Best regards
Marcus
Am 27.10.2014 um 07:56 schrieb irwan.husein <ir...@gmail.com>:
> Hi All,
> i'm flex + php developer since flex 4.6
> today i'm start migrating old amfphp server (1.9) to amfphp 2.2.1 + flex
> 4.13
>
> unfortunately, i've found some problems
> in amfphp 1.9, i can do remote call like this
>
> *Flex Client :*
> public var gateway:NetConnection;
>
> var PHPParam:Object = new Object;
> PHPParam.Parameter00 = 'param1';
> PHPParam.Parameter01 = 'param2';
> PHPParam.Parameter02 = 'param3';
>
> gateway.call("someservice.somefunction", new Responder(resultData,
> null),PHPParam);
>
> *AMFPHP Services*
>
> function somefunction($PHPParam)
> {
> $Param1 = $PHPParam['Parameter00'];
> $Param2 = $PHPParam['Parameter01'];
> $Param3 = $PHPParam['Parameter02'];
>
> //do something
> return "something";
> }
>
> but, in AMFPHP 2.2.1, i can't do it anymore, i can't sent object to php
> services, only simple parameter.
> in their website, they suggest using JSON statement, but theres no example
>
> if anyone has ever experienced ?
> or we just go with ValueObject approach?
>
> regards,
> Irwan
>
>
>
> --
> View this message in context: http://apache-flex-users.2333346.n4.nabble.com/Flex-AMFPHP-2-2-1-tp8506.html
> Sent from the Apache Flex Users mailing list archive at Nabble.com.