Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:33537 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 12041 invoked by uid 1010); 30 Nov 2007 02:16:11 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 12024 invoked from network); 30 Nov 2007 02:16:11 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 30 Nov 2007 02:16:11 -0000 Authentication-Results: pb1.pair.com smtp.mail=xuefer@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=xuefer@gmail.com; sender-id=pass; domainkeys=bad Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.146.181 as permitted sender) DomainKey-Status: bad X-DomainKeys: Ecelerity dk_validate implementing draft-delany-domainkeys-base-01 X-PHP-List-Original-Sender: xuefer@gmail.com X-Host-Fingerprint: 209.85.146.181 wa-out-1112.google.com Received: from [209.85.146.181] ([209.85.146.181:28505] helo=wa-out-1112.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 1B/8E-32949-A627F474 for ; Thu, 29 Nov 2007 21:16:10 -0500 Received: by wa-out-1112.google.com with SMTP id l24so2641074waf for ; Thu, 29 Nov 2007 18:16:07 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=Wlbw4PwVt8HEQ7zWOx+1wv6kQPoROQGgDt8yrZY8EhA=; b=A7Ghr3/XWjhTTVMHckvtj48XbmmyiRLN6oWIP8IDkyFcG1+JUn90isRGsIxHdHtLNdsL9Lzt9LL0QWAGkwnr5Fc6g/pyZU2SKFCrLiq3ZZKMKOvPXHpM6dpCUAwGZ5sFQJReWCJZKoiJvoNyVtaLW/DDVR3EpN3f0H3drKqXqv0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=su8A06PxDnMVffciOMipWR/K1IUFbpaajL30RyDUM5nYyNrCkSzgrTGLVjCE3t4fS62sAXQCs2vjhV4ioz2JhWXgJ90/MEz8KgCaiEZQs7bNZarVupqu1oAZh2xNDR0H5IZb+Zja5DS5YUF22t5KncVzcxZ0v+AhXi4dlG1p4lw= Received: by 10.114.166.1 with SMTP id o1mr727021wae.1196388967845; Thu, 29 Nov 2007 18:16:07 -0800 (PST) Received: by 10.114.27.6 with HTTP; Thu, 29 Nov 2007 18:16:07 -0800 (PST) Message-ID: <28139bc0711291816u1bad67eaw4cd4cdf664c13818@mail.gmail.com> Date: Fri, 30 Nov 2007 10:16:07 +0800 To: "Stanislav Malyshev" Cc: "Sara Golemon" , omar@php.net, "PHP Internals" In-Reply-To: <474F5F75.3030808@zend.com> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <474F0EE7.8020201@php.net> <474F4E47.8050506@zend.com> <474F5E12.1050404@php.net> <474F5F75.3030808@zend.com> Subject: Re: [PHP-DEV] Proposed feature for json_encode() From: xuefer@gmail.com (Xuefer) if we want to we should do echo htmlspecialchars(json_encode($stringValue)) instead actually, and yes JSON_HEX_TAG will help avoiding htmlspecialchars() just like urlencode()ed data which never contains < > or so. i'm not sure if there is problem if you put json_encode()ed data in