Re: Casting a PHP type, new SAPI

Hi Ingwie, I fail to see why this would be considered a SAPI? It doesn't seem to integrate with application code written in another language to exchange data between php userland and local application variables. Just seems like you're trying to accomplish a dedicated server/daemon that listens for messages on a TCP port with a self developed JSON protocol and answers according to that protocol. If that is what you are trying to accomplish you could do that easily in PHP userland using CLI. Much better approach would be using such a CLI script together with an event based messaging system waiting for incoming messages using technologies like gearman, activemq, kafka, etc. This would give you so much more power in ways of load balancing, fail-over and/or replication and multi language support that I see no use for JRP, as all can be done within a matter of hours using regular existing PHP extensions and the CLI executor. Bas van Beek > Op 20 jan. 2015, om 06:36 heeft Kevin Ingwersen (Ingwie Phoenix) > <ingwie2000@googlemail.com> het volgende geschreven: > > Good morning, everyone. > > Today I have started to concept a new SAPI which I have wanted to do in quite a while now. To > learn more, here is a README: > https://github.com/IngwiePhoenix/php-jrp/blob/master/README.md > <https://github.com/IngwiePhoenix/php-jrp/blob/master/README.md> > > But in order for me to work this out as good as I can - especially the PHP API at the bottom - > I need to know just a thing I could not find within the public PHP headers: When I have an Array, > now can I turn that into an object? > > I’d be happy to hear what you think of this concept as well. As mentioned in the README, > process on this will begin later. For now, I am going to use helper libraries, but late ron I want > to strip the project to lesser and lesser dependencies. But it will remain being written in C++. > > Kind regards, > Ingwie