Received: by 10.101.19.6 with SMTP id w6mr259376ani.23.1323736837919;
        Mon, 12 Dec 2011 16:40:37 -0800 (PST)
X-BeenThere: json-rpc@googlegroups.com
Received: by 10.150.245.19 with SMTP id s19ls28945ybh.5.gmail; Mon, 12 Dec
 2011 16:40:37 -0800 (PST)
Received: by 10.101.137.37 with SMTP id p37mr259369ann.17.1323736837360;
        Mon, 12 Dec 2011 16:40:37 -0800 (PST)
Received: by 10.101.137.37 with SMTP id p37mr259367ann.17.1323736837342;
        Mon, 12 Dec 2011 16:40:37 -0800 (PST)
Return-Path: <wickedlo...@gmail.com>
Received: from mail-gx0-f187.google.com (mail-gx0-f187.google.com [209.85.161.187])
        by gmr-mx.google.com with ESMTPS id n75si5317083yhe.3.2011.12.12.16.40.37
        (version=TLSv1/SSLv3 cipher=OTHER);
        Mon, 12 Dec 2011 16:40:37 -0800 (PST)
Received-SPF: pass (google.com: domain of wickedlo...@gmail.com designates 209.85.161.187 as permitted sender) client-ip=209.85.161.187;
Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of wickedlo...@gmail.com designates 209.85.161.187 as permitted sender) smtp.mail=wickedlo...@gmail.com
Received: by ggnk4 with SMTP id k4so8050739ggn.24
        for <json-rpc@googlegroups.com>; Mon, 12 Dec 2011 16:40:37 -0800 (PST)
MIME-Version: 1.0
Received: by 10.236.129.238 with SMTP id h74mr49887yhi.1.1323736837275; Mon,
 12 Dec 2011 16:40:37 -0800 (PST)
Received: by d17g2000yql.googlegroups.com with HTTP; Mon, 12 Dec 2011 16:40:37
 -0800 (PST)
Date: Mon, 12 Dec 2011 16:40:37 -0800 (PST)
In-Reply-To: <CAHd-4wD+6jcqu4RJ34bcc=kEyuRWg4UhBea+zEdUQ9uQ4BZRrQ@mail.gmail.com>
References: <CAHd-4wD+6jcqu4RJ34bcc=kEyuRWg4UhBea+zEdUQ9uQ4BZRrQ@mail.gmail.com>
User-Agent: G2/1.0
X-HTTP-UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_6_8)
 AppleWebKit/535.7 (KHTML, like Gecko) Chrome/16.0.912.63 Safari/535.7,gzip(gfe)
Message-ID: <9bdddb38-6192-4c8e-9d34-9760d9bc60a8@d17g2000yql.googlegroups.com>
Subject: Re: Inconsistence in error message between spec and example
From: "Matt (MPCM)" <wickedlo...@gmail.com>
To: JSON-RPC <json-rpc@googlegroups.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Thank you for pointing this out, I have updated the example in the
specification at jsonrpc.org.

--
Matt (MPCM)

On Dec 9, 1:23=A0pm, Leandro Santiago <leandrosansi...@gmail.com> wrote:
> In the specification, the error message with code =A0-32601 is "Method
> not found", but in the example it's written "Procedure not found.".
>
> --
> Atenciosamente,
> Leandro