todo:ext:wddx
Differences
This shows you the differences between two versions of the page.
Next revision | Previous revision | ||
todo:ext:wddx [2008/12/02 10:41] – created magicaltux | todo:ext:wddx [2017/09/22 13:28] (current) – external edit 127.0.0.1 | ||
---|---|---|---|
Line 3: | Line 3: | ||
The main problem for packets generation is the values types. Wddx supports a range of types including common types also found in PHP (array, struct, string, boolean, number, null, and binary with PHP 6), but also some types specific to Wddx, including dateTime and recordSet. | The main problem for packets generation is the values types. Wddx supports a range of types including common types also found in PHP (array, struct, string, boolean, number, null, and binary with PHP 6), but also some types specific to Wddx, including dateTime and recordSet. | ||
- | ==== dateTime | + | ==== WDDX types ==== |
- | The new DateTime php object could be automatically serialized. | + | === dateTime === |
- | NB: Wddx is missing a " | + | The new DateTime php object could be automatically serialized to the dateTime wddx type. |
+ | |||
+ | NB: Wddx is missing a " | ||
Problems: | Problems: | ||
Line 15: | Line 17: | ||
* Already existing :) | * Already existing :) | ||
- | ==== recordSet | + | === recordSet === |
A recordSet is like a table (ie. a numerically-indexed array containing in each row arrays with always the same columns). | A recordSet is like a table (ie. a numerically-indexed array containing in each row arrays with always the same columns). | ||
Line 21: | Line 23: | ||
The implementation currently converts everything to arrays. | The implementation currently converts everything to arrays. | ||
- | ==== Binary data ==== | + | === Binary data === |
WDDX offers the ability to transfer binary data (base64 encoded). There is currently no way to encode data in this format. | WDDX offers the ability to transfer binary data (base64 encoded). There is currently no way to encode data in this format. | ||
Line 29: | Line 31: | ||
* Autodetecting invalid UTF-8 sequences, and treat them as binary data | * Autodetecting invalid UTF-8 sequences, and treat them as binary data | ||
* Finding a way to force a value to binary | * Finding a way to force a value to binary | ||
+ | |||
+ | ==== Possibilities ==== | ||
+ | |||
+ | === New class approach === | ||
+ | |||
+ | Create a new WddxValue class, with a " | ||
+ | |||
+ | The class would implement ArrayAccess, | ||
+ | |||
+ | <code php> | ||
+ | |||
+ | === Native types === | ||
+ | |||
+ | Problems: | ||
+ | * Types string and binary can't be determined without testing the UTF-8 validity of the provided data. | ||
+ | * Type resultSet can't be represented with php's native types | ||
+ | * PHP's DateTime type is not compatible with current behaviour of the Wddx ext. | ||
+ | |||
+ | === Hybrid solution === | ||
+ | |||
+ | * Create WddxBinaryString (only for PHP < 6) and a WddxResultSet classes | ||
+ | * Accept DateTime class for datetime values | ||
+ | |||
+ | Problems: | ||
+ | * DateTime can't be treated as it was before (current implementation returns an unix timestamp). Creating a castable WddxDateTime class would solve this issue. | ||
+ | |||
+ | ===== PHP6 support ===== | ||
+ | |||
+ | Input (XML) string should be UTF-8 encoded. In the case of unicode string, encoding is irrelevant, however for binary string we need to force utf-8 (with UG(utf8_conv)) | ||
+ | |||
+ | Input variables/ |
todo/ext/wddx.1228214509.txt.gz · Last modified: 2017/09/22 13:28 (external edit)