Re: Call for Votes: JSON location

Bonsoir, Matthew Weier O'Phinney wrote:

On 4/7/06, Daniel Convissor <danielc@analysisandsolutions.com> wrote:

The JSON class has been waiting some time for a decision on which category is best. So, let's do a quick vote, please. I'll tally them up on Tuesday afternoon, America/New York time.

I'm jumping in just under the gun, it seems...

Here are the options: Services/JSON HTML/JSON Text/JSON JSON/JSON JSON/Encode|Decode|RPC

I like this last option -- I have a lot of use for encoding to JSON, very little for decoding JSON (why not just use a POST or GET request to a PHP script, and send back JSON)? So it's not related to php direct.

However, this is still an option with placement in the other locations. Since AJAX support is going in as HTML_AJAX, JSON was bundled in there just because needed

for consistency, it would make sense to put it in the HTML category. However, I really think this is unfortunate. While javascript is primarily used with HTML, it's getting some leverage with XUL and other areas, making it less domain specific to X/HTML. ok

It *is* a text-based format, but, in this case I think the Text category is too generic for this purpose. Bytes category then ...

JSON is only a service insomuch as typically you'll be setting up some sort of proxy service for handling JSON calls and passing them on to APIs (in this case, the script handling the JSON becomes a Controller). Aren't we all on Services ?

Why isn't there a Javascript category? It doesn't need to be used for actual javascript (and thus diluting PEAR's purpose), but could be used for PHP that supports or generates Javascript actions -- AJAX, JSON, etc. I ask for a role "javascript" or at least "public", that is not related to category as you say.

Just my 2 pieces of currency. 2 pieces ?

is it summer ? :) -- toggg