Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:50557
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain zend.com designates 63.205.162.117 as permitted sender)
To: "internals@lists.php.net" <internals@lists.php.net>
Thread-Topic: Performance of buffer based functionality (JSON, AES,
 serialize())
Thread-Index: AcuMyKPxquXeaFi0QPSLqa5adhX35w==
Date: Thu, 25 Nov 2010 17:47:10 +0000
Message-ID: <8757232E56758B42B2EE4F9D2CA019C9154CB7@US-EX2.zend.net>
Accept-Language: en-US
Content-Language: en-US
Content-Type: multipart/alternative;
	boundary="_000_8757232E56758B42B2EE4F9D2CA019C9154CB7USEX2zendnet_"
MIME-Version: 1.0
Subject: Performance of buffer based functionality (JSON, AES, serialize())
From: andi@zend.com (Andi Gutmans)

--_000_8757232E56758B42B2EE4F9D2CA019C9154CB7USEX2zendnet_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi,

Completely different topic :)

I've been looking a bit into performance around json encoding, hashing+encr=
yption (aes) and serialize()/unserialize(). Data that is marshaled and ofte=
n transmitted over the wire.

I know there have been some high-end apps that have benefited from some cus=
tom serializers, etc... (typically platform dependent).
I wonder if people here think improvements in these areas would move the ne=
edle for the majority of mainstream apps or not.

Thanks,

Andi

--_000_8757232E56758B42B2EE4F9D2CA019C9154CB7USEX2zendnet_--