Re: [Resin-interest] AMFPHP on Quercus

2010-03-17 Thread Brian Topping
On Mar 5, 2010, at 12:35 PM, Emil Ong wrote: > On Fri, Mar 05, 2010 at 11:57:05AM -0500, Brian Topping wrote: >> >> Am I missing anything obvious? > > I don't think so. I'll file this as a bug - there might be an easy > fix. > > http://bugs.caucho.com/view.php?id=3926 > > Invoking the PHP from

Re: [Resin-interest] AMFPHP on Quercus

2010-03-05 Thread Emil Ong
On Fri, Mar 05, 2010 at 11:57:05AM -0500, Brian Topping wrote: > Thanks Emil. That makes some sense, but as I think about it, I'm not > sure I understand how to wire these together. Blaze is obviously > Java, and the point of any of these RPC abstractions is to instantiate > a remote servic

Re: [Resin-interest] AMFPHP on Quercus

2010-03-05 Thread Brian Topping
Thanks Emil. That makes some sense, but as I think about it, I'm not sure I understand how to wire these together. Blaze is obviously Java, and the point of any of these RPC abstractions is to instantiate a remote service bean and call methods. PHP can instantiate Java easily enough, but

Re: [Resin-interest] AMFPHP on Quercus

2010-03-04 Thread Emil Ong
Hi Brian, I think your best bet is to use BlazeDS. As far as I know, nobody has used AMFPHP with Quercus, but using BlazeDS would be simple (just use new Java("some.blazeds.Clazz", "first arg", "etc") to create objects). You could also try using Hessian Flash, but then you'd need your objects to

[Resin-interest] AMFPHP on Quercus

2010-03-04 Thread Brian Topping
Greetings, I'm just getting started with Quercus and am in a situation where an existing application is using AMFPHP. Looking at the client packets that AMFPHP is storing in the logs, they appear to be well-formed. When I look at them on the wire with Wireshark, they have Java class name