Decoding became 10x faster than before!
I'm an enthusiastic web developer from Belgium, interested in all new internet technologies and tricks.
@markusstaab @derickr Fun fact, -you can use the encoding package to build a soap-server as well ;)
It contains everything you need already.
@derickr It's very commonly used, so I'dd say it's still essential for a lot of people.
@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!
Happy once-in-a-four-year exotic bug fix day!
Started a discussion about fixing the DOM extension spec compliance: https://externals.io/message/122169
Feel free to chime in :)
In v3 of veewee/xml, the Reader component gets an improved API focussing on you getting stuff done!
The work on the new tool for installing PHP extensions is in full swing.
We had a productive meeting at
@SymfonyCon, and online calls with @derickr, @seldaek, @naderman, @alcaeus, @nicolasgrekas, @asgrim.
See the updated requirements document 👉https://docs.google.com/document/d/1_N0E9xo3jn9aKrIZHIbTYaY5lXw71BpSO6-it4cRpDo/edit#heading=h.qi4yl6hz8u32
Key design updates:
- Using composer.json for requirements.
- Extension is a Composer package with `ext-php` type.
- For PoC, we'll use GitHub, but later we plan to use http://packagist.org as a registry.
@Pol Sad to hear. Take care!
Excited to launch our first @sulu bundle:
We wish you a clear overview of your failed messenger tasks!
https://github.com/tailrdigital/sulu-messenger-failed-queue-bundle
Only one more sleep before #symfonycon!
See you there!
I'd like to get the spec compliance bugs fixed in ext-dom for PHP 8.4. Normally that wouldn't be possible as the BC break would be too huge. However, we now have new classes in the DOM namespace as a result of the HTML5 RFC.
I'd like to propose to switch to a "spec-compliant mode" when one of those new DOM\HTMLDocument or DOM\XMLDocument classes are used.
This way, existing code will keep on functioning while new code can enjoy spec compiance.
The cool part about this is : it can use the same code for (de)hydrating both regular fully typed objects and unkown objects.
Reflecta can now also read class attributes and assign dynamic properties through its lenses!
Decided to put some extra love into writing XML today.
I benchmarked #PHP's native serializer vs code export. You won't believe what I found!
https://peakd.com/hive-168588/@crell/benchmarking-serialization