| GitHub | https://github.com/veewee/ |
| Blog | https://veewee.github.io/ |
| GitHub | https://github.com/veewee/ |
| Blog | https://veewee.github.io/ |
@markusstaab @derickr Fun fact, -you can use the encoding package to build a soap-server as well ;)
It contains everything you need already.
@derickr There are many bugs that have been open for years, especially in the HTTP layer but also in the encoding layer.
Too many to address in a toot anyways ;)
For this part I am working on right now, I think the lack of type information, xml namespace support and the limitations of the type converters are the main reasons for the moves we are making in php-soap.
A short-list of problems it solves:
Launched soap-client v4 -alpha
This release now contains a pure PHP SOAP encoder so that you don't need php's SOAP extension anymore.
https://github.com/phpro/soap-client/releases/tag/4.0.0-alpha1
I would love to receive some early feedback so that we can fix obvious bugs before an official release.
@nielsdos Thanks for all the work you did. It was a pleasure to work with you in the previous months.
Take care!
Launched an initial experimental version of the new SOAP encoder package. Feel free to play around with it!
In v3 of veewee/xml, the Reader component gets an improved API focussing on you getting stuff done!