|  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login
Request #43308 Functions to use registered serializer handlers to serialize and unserialize
Submitted: 2007-11-15 22:29 UTC Modified: -
Avg. Score:4.6 ± 0.8
Reproduced:4 of 4 (100.0%)
Same Version:1 (25.0%)
Same OS:1 (25.0%)
From: jani dot ollikainen at pronetko dot fi Assigned:
Status: Open Package: Feature/Change Request
PHP Version: 5.2.5 OS: Linux
Private report: No CVE-ID: None
View Add Comment Developer Edit
Welcome! If you don't have a Git account, you can't do anything here.
You can add a comment by following this link or if you reported this bug, you can edit this bug over here.
Block user comment
Status: Assign to:
Bug Type:
From: jani dot ollikainen at pronetko dot fi
New email:
PHP Version: OS:


 [2007-11-15 22:29 UTC] jani dot ollikainen at pronetko dot fi
Ok, Tried this once with feature request #42725
and no go. Second try..

First read the #42725 and then read this:

Of course I know those, but those don't unserialize() data which is
formatted like:


And there are many different serializer handlers in php, for example:
Registered serializer handlers => php php_binary wddx

So there should be functions which can use those registered serializer
handlers to serialize/unserialize data accordingly selected serializer

So I don't think that this is bogus feature request.
Prove me wrong, but serialize/unserialize isn't the answer.


Add a Patch

Pull Requests

Add a Pull Request


AllCommentsChangesGit/SVN commitsRelated reports
 [2008-12-19 17:56 UTC] emil dot hall at gamereactor dot se
You get one vote from me! This is far from bogus. And here is a simple test case:

echo serialize($_SESSION), "\n";
echo file_get_contents('/path/sess_'.session_id());

If the advice from was solid, I would expect the exact same output from both echoes.

Actual result:
PHP Copyright © 2001-2021 The PHP Group
All rights reserved.
Last updated: Sat Jan 23 18:01:26 2021 UTC