[ 
https://issues.apache.org/jira/browse/THRIFT-1380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dave Watson updated THRIFT-1380:
--------------------------------

    Attachment: 0008-Thrift-Write-only-PHP-serialization-protocol.patch
    
> Thrift: Write-only PHP serialization protocol

> ----------------------------------------------
>
>                 Key: THRIFT-1380
>                 URL: https://issues.apache.org/jira/browse/THRIFT-1380
>             Project: Thrift
>          Issue Type: Improvement
>          Components: C++ - Library
>            Reporter: Dave Watson
>            Priority: Minor
>         Attachments: 0008-Thrift-Write-only-PHP-serialization-protocol.patch
>
>
> From c9cd369f4352472f62b1b1f23dd3bee122c97b14 Mon Sep 17 00:00:00 2001
> From: David Reiss <[email protected]>
> Date: Mon, 10 May 2010 19:17:11 +0000
> Subject: [PATCH 8/9] Thrift: Write-only PHP serialization protocol
> Summary:
> - It's a bit sloppy, but not too bad.
> - It will happily serialize data that cannot be represented in PHP (like
>   maps with lists as keys).
> - No support for sets.
> - The hardest part is getting the "keys" right for a list.
> davejwatson: also added to Makefile.am
> Test Plan:
> Used it to serialize some not-totally-trivial data and PHP was happy
> with it.  
> Revert Plan:
> ok
> ---
>  lib/cpp/Makefile.am                            |    2 +
>  lib/cpp/src/protocol/TPhpSerializeProtocol.cpp |  212 
> ++++++++++++++++++++++++
>  lib/cpp/src/protocol/TPhpSerializeProtocol.h   |  114 +++++++++++++
>  3 files changed, 328 insertions(+), 0 deletions(-)
>  create mode 100644 lib/cpp/src/protocol/TPhpSerializeProtocol.cpp
>  create mode 100644 lib/cpp/src/protocol/TPhpSerializeProtocol.h

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to