Migrating JSON-RPC specifications...

23 views
Skip to first unread message

Sin-young "Divinespear" Kang

unread,
Oct 9, 2009, 12:29:49 PM10/9/09
to JSON-RPC
(excuse my bad english...)

I just started migrating JSON-RPC specifications using RSpec.
I wish it helped to make specification to more clearer and more
specifically.

also I have plan to implement JSON-RPC for Ruby based this work.

project site not opened yet, but will be soon.
(rubyforge, google, or other hosting? plz suggest me. I don't have
idea.)

sure any discussions or advices are welcome.


Here is example of JSON-RPC spec 2.0 to RSpec doc:
------------------------------------------------------------------------------------------------------------------
(in /home/divinespear/dev/srcs/lib/json-rpc-specs)

Message
- is Object.
- accept following fields.
- ignore all other fields.

Message to Request: field "jsonrpc"
- is required.
- is String.
- MUST be "2.0".

Message to Request: field "method"
- is required.
- is String.
- is method name to be invoked.
- note: method name begins with "rpc." is reserved for rpc-internal.

Message to Request: field "params"
- is optional
- can be omitted when empty.
- is Array or Object.

Message to Request: field "id" for normal request
- is required.
- is String, Number, True, or False.
- MUST NOT be Null.
- SHOULD NOT contain fractional parts when type is Number.

Message to Request: field "id" for notification
- is optional
- can be omitted.
- MUST be Null if not omitted.

Message to Response: field "jsonrpc"
- is required.
- is String.
- MUST be "2.0".

Message to Response: field "id"
- is required.
- is String, Number, True, or False.
- is request "id".
- is Null when raised error before detecting request "id".
- SHOULD NOT contain fractional parts when type is Number.

Message to Response: field "result"
- is required.
- is value that returned by invoked method.
- MUST be omitted when message has "error".

Message to Response: field "error"
- is required.
- is ErrorObject.
- MUST be omitted when message has "result".
------------------------------------------------------------------------------------------------------------------

Regards,
Sin-young "Divinespear" Kang <divin...@gmail.com>

Sin-young "Divinespear" Kang

unread,
Oct 10, 2009, 6:33:43 AM10/10/09
to JSON-RPC
I create project site to
http://code.google.com/p/json-rpc-spec/

any discussions or contributions are welcome.

Lorenzo Pastrana

unread,
Oct 11, 2009, 3:04:36 PM10/11/09
to json...@googlegroups.com
'You' started migrating what ??
Thanks not to come back with 'migrations' issues.

I dunno where the hell this guy comes from..

The official place to discuss JSON RPC is here (http://groups.google.com/group/json-rpc) And nowhere else.
Period.

esavard

unread,
Oct 11, 2009, 6:34:12 PM10/11/09
to JSON-RPC
Hi,

I'm new to the list and I must admit that I'm not impress by Lorenzo's
response to Sin-young...

Wow... This is definitely not the kind of (impolite) attitude I expect
from any active member of any Open Source community!

May be a more friendly approach could have been to point out that
there is already other implementations of JSON-RPC for Ruby out there
like: http://orbjson.rubyforge.org/ and invite the poor guy to join
those projects?

I see no need to be rude with him. It's not like we was posting about
Viagra pills or something else not related to JSON-RPC.

Matt (MPCM)

unread,
Oct 11, 2009, 6:40:47 PM10/11/09
to JSON-RPC
@Sin-young "Divinespear" Kang

Might want to change your google code project name to reflect the r-
type aspect of your work, perhaps json-rpc-rtype instead of json-rpc-
spec.

Between the language differences there seems to be some confusion over
what you are attempting.

--
Matt (MPCM)

Lorenzo Pastrana

unread,
Oct 11, 2009, 7:28:06 PM10/11/09
to json...@googlegroups.com
On Sun, 2009-10-11 at 15:34 -0700, esavard wrote:
>
> I see no need to be rude with him. It's not like we was posting about
> Viagra pills or something else not related to JSON-RPC.

Well, in open source communities as well as in others, I consider VERY
RUDE to stomp-in and, not introducing yourself, nor your work nor
intentions, and tell people that you have some kind of better way to do
things that people have come to the hard way (we've been working on this
for about two years now and didn't read a single post from the 'Divine
Spear'), then create side groups with name clashes and finally invite to
join.

Oh, yes rude me !

Try make a nice party at your place, work hard making flyers, invite
your friends and some selected cuties, cook good food & mix cocktails,
bring in your better records and a big sound system let the party begin
and people start to dance ... Then at midnight comes a guy that nobody
knows, he turns the sound down and yell 'Hi everybody, my name is "God's
Hand", and you know what ? Your party could be nice if it was at my
place, just come over'.

Haha ... Yes guy ! Keep nice and friendly, come on ;P

Cheers

esavard

unread,
Oct 11, 2009, 10:04:43 PM10/11/09
to JSON-RPC
Lorenzo, I see your point but I still think that you were quick to
jump on the conclusion that Sin-young wanted to hijack the JSON-RPC
project... He introduced himself and mentionned that he didn't write
English well. So, you should have read between the lines.

I think Matt (MPCM) got it and replyed accordingly.

For your info, RSPEC (http://rspec.info) is a Behaviour Driven
Development framework for Ruby which is used to write stories to
valide code in a meaningfull way. Unit testing kind of... There is no
way you can re-implement JSON-RPC in RSPEC. But, if it is really what
Sin-young wants to do, I think it could be usefull. It could be used
to validate that a Ruby JSON-RPC implementation is 100% compliant with
the specification.

I must agree with Matt that the project name is not well choosen and
could lead to some confusion... and misunderstanding!

Lorenzo Pastrana

unread,
Oct 12, 2009, 3:28:22 AM10/12/09
to json...@googlegroups.com
On Sun, 2009-10-11 at 19:04 -0700, esavard wrote:
I must agree with Matt that the project name is not well choosen and
could lead to some confusion... and misunderstanding!
... condescendence is so cute ..

Lorenzo Pastrana

unread,
Oct 12, 2009, 3:42:10 AM10/12/09
to json...@googlegroups.com

I'm looking for posts from you before this couple actually, well I can't find a single one ...

So wellcome you too, that don't know people, presume of their ignorance, and tell how they should behave, I'm sure you'll make plenty of friends in communities, your future is some kind of written.

Why is that : guys like Sin-young alway have guys like you for friend ... symbiotic forms of life ?

Lo.


On Sun, 2009-10-11 at 19:04 -0700, esavard wrote:

Alexandre Morgaut

unread,
Oct 12, 2009, 3:52:33 AM10/12/09
to JSON-RPC
HI,

I was kind of frightened too when I received this post saying
"Migrating JSON-RPC specifications"
I can understand Lorenzo reaction even if I didn't write it ;-)

Sure you, "Divinespear", didn't choose the right word as title for
your post.
Maybe "Creating RSpec version of JSON-RPC" would have been really
better

Thanx Matt for your suggestion to rename its project, I wouldn't want
people being confused and Sure that it would be a good thing if he
could set a link to this official JSON-RPC group on its Google code
repository (which I strangely can't access this morning)

By the way, It would be good to have a page listing interesting
projects around JSON-RPC like Douglas Crockford did for JSON. It helps
specification to be recognized as a standard before it becomes an
official RFC, ISO, or W3C recommendation ;-)

About this RSpec (I'm happy to have learn what it is), I think I see
at least one error that should be corrected :

Message to Request: field "id" for notification
- is optional
- can be omitted.
- MUST be Null if not omitted.

Well in this case, field "id"
- Must be omitted

PS: Lorenzo... "y is that : guys like Sin-young alway have guys like
you for friend ... symbiotic forms of life ?" Your're killing me.. ROTF

Alexandre Morgaut

unread,
Oct 12, 2009, 4:06:15 AM10/12/09
to JSON-RPC
I forgot,

Welcome Sin-young, as I said, you're project can surely be
interesting, even if don't use ruby, I think I'll take a closer look
to RSpec.

Welcome Etienne (Are you French ?), thanx for your precisions on what
RSpec is. If you know Sin-young like it looks to be, don't hesitate to
invite him posting back here and express himself a little more on its
project. I'm sure we all agree that every project using JSON-RPC is
interesting, and even more if their actors expose them here to make it
known and eventually be aware of some implementation errors...

Alexandre.

Sin-young "Divinespear" Kang

unread,
Oct 12, 2009, 2:02:30 AM10/12/09
to JSON-RPC
@esavard

Yes, I WILL do that. thanks to understand my goal.
I wish my work could help to JSON-RPC community.

@Matt (MCPM)

Thanks an advice. it could be confused to some pepoles...
so I closed old one and reopened to http://code.google.com/p/json-rpc-rspec-migration/

Sin-young "Divinespear" Kang

unread,
Oct 12, 2009, 7:05:20 AM10/12/09
to JSON-RPC
@Matt (MCPM)
Thanks your advice, It should be confused to many people.
so I closed old one and reopened to http://code.google.com/p/json-rpc-rspec-migration/

@Alexandre Morgaut, @esavard
Thanks for interest my project.
I have deep interest about JSON-RPC, so I just want help it.

please tell me any discussions or advices at any time, it's always
welcome.

@Lorenzo Pastrana
I never want breake JSON-RPC. it's separated project.

Etienne Savard

unread,
Oct 12, 2009, 12:42:46 PM10/12/09
to json...@googlegroups.com
@Lorenzo

Are you mad at me? :) 

Has I wrote before: I just joined the JSON-RPC mailing list a couple of days ago, so you can stop searching for previous posts you wouldn't find any. 

If you ask why I join the list (I know, you didn't asked but I will tell you anyway): it is because I wish to implement a Qt JSON-RPC (compliant to the v2 specification) using an existing Qt JSON library (http://qjson.sourceforge.net/).  I'm also interested to use it in Ruby on Rails projects.

I thought that the mailing list will be a great way to stay connected with people using the specification and/or writing it.  A good place to ask questions, to interact.  I still think it is.

Now, I will answer the questions you asked me so kindly:

So welcome you too, that don't know people,
 
Thank you for welcoming me is such a friendly and warmfull way.  It must be really nice to be your friend.  Now I do know you a little more.
 
presume of their ignorance,

So you did know about RSpec?  Good for you, it is such a great tool.  In fact, I was posting the link and explaining what RSpec is because some other people on the list may not be aware of what it is.  Please, don't take it personal.  I never presumed anything about you...
 
and tell how they [people] should behave,

Yes, I did told **YOU** how you should behave.  Don't include everyone else in this.  Reading their comments on this thread, they apparently know how to behave.  You don't.
 
I'm sure you'll make plenty of friends in communities, your future is some kind of written.

You are a funny guy!  In fact I have already made a couple of good friends in the Open Source Community.  Thanks for your concerns about my future.  It's really nice of you.   

Why is that : guys like Sin-young alway have guys like you for friend ... symbiotic forms of life ?

Lorenzo, you don't know me and you don't know Sin-young either.  I was just reacting to the way you jump on Sin-young without asking questions (I dunno where the hell this guy comes from), without asking him to clarify it's ideas.  I tend to have friends that are humble, that are curious and open towards others... call it symbiosis if you want! 

May be I spend to much time with those Ubuntu's punks with their motto: "Humanity towards others"  ;)


@Alexandre
Oui, je suis francophone.  Je suis du Québec, Canada.  Désolé d'avoir pris part dans une discussion houleuse comme celle-là...  J'ai compris l'idée de Sin-young et je trouvais dommage qu'il se fasse sauter dessus comme ça sans raison.  Je participe à plusieurs mailing list et je vois rarement une telle attitude.  Encore désolé d'avoir mis de l'huile dans le feu!

@Sin Young
I find your project interesting and hope to see more of that soon.  I'm still pretty new to Ruby but I like it.  I will surely subscribe on your new mailing list.

Etienne.

2009/10/12 Lorenzo Pastrana <past...@ultraflat.net>

esavard

unread,
Oct 12, 2009, 1:13:24 PM10/12/09
to JSON-RPC
Hi Sin-young,

Do you know about Orbjson (http://orbjson.rubyforge.org/)? It's an
implementation of JSON-RPC in Ruby. You could try to use your RSpec
specification with it to validate it. I don't know if this
implementation is compliant with V2 of the JSON-RPC spec or not. I
can't find anywhere in the documentation a place where they mention
which revision they support.

May be you could contribute code back to them when Orbjson is 100%
compliant with JSON-RPC version 2 and documented with RSpec?

Unless you really want to implement a new JSON-RPC for Ruby.

Étienne.

On 12 oct, 07:05, "Sin-young \"Divinespear\" Kang"
<divinesp...@gmail.com> wrote:
> @Matt (MCPM)
> Thanks your advice, It should be confused to many people.
> so I closed old one and reopened tohttp://code.google.com/p/json-rpc-rspec-migration/

Sin-young "Divinespear" Kang

unread,
Oct 12, 2009, 3:19:38 PM10/12/09
to JSON-RPC
@esavard
That's good point to work! Thanks to advice it. :D
But I'll work my own implementation someday cause my idea is pritty
diffrent with Orbjson.

I'm currently upgrading my laptop to Ubuntu 9.10 so still not started
yet.

Etienne Savard

unread,
Oct 12, 2009, 4:31:45 PM10/12/09
to json...@googlegroups.com
@Sin-young

It's a good thing that you eventually start a new implementation of JSON RPC for Ruby because there is not much activity on Orbjson (no new release since 2005)...  The project seems pretty dead to me.

Étienne. 

2009/10/12 Sin-young "Divinespear" Kang <divin...@gmail.com>

Lorenzo Pastrana

unread,
Oct 12, 2009, 5:36:21 PM10/12/09
to json...@googlegroups.com
On Mon, 2009-10-12 at 12:42 -0400, Etienne Savard wrote:

> Now I do know you a little more.

We're getting to know you too ...

> Please, don't take it personal. I never presumed anything about
> you...

Well if you don't want me to take it personal don't start your post with
my name ... right ?

> Reading their comments on this thread, they apparently know how to
> behave. You don't.

I can't believe it ! In fact I was wrong, the symbiote is the plague
actually ...

You won't tell me I didn't warned you guys.

> You are a funny guy!

Everybody on this list knows I'm not !
Everybody knows I'm fair too.

> I tend to have friends that are humble, that are curious and open
> towards others...

Well I'm not THAT tolerant to toxic people ... Take it for granted.
Everybody on this list knows now, what an arrogant guy you are.

Why is that : the more arrogant and pretentious a guy is, the more he
ask others to be huuuummble ?

For you information you didn't participate to an argument you
started it! And don't try to say you're sorry because you're not, I'm
pretty sure you feel even more important now.

Please take this private if you have more concerns about me.

Lorenzo


Sin-young "Divinespear" Kang

unread,
Oct 13, 2009, 12:48:08 PM10/13/09
to JSON-RPC
@Lorenzo Pastrana
I'm sorry about that. I should ask before I said.
and I may choosed wrong words to talk my work...

Lorenzo Pastrana

unread,
Oct 13, 2009, 3:47:00 PM10/13/09
to json...@googlegroups.com

Well, I'm sorry to be the bad one ... I just felt I had to do something
to disspate any confusion promptly when I saw your message ... Then came
another guy and things got heavy ...

Lo.

Jeffrey Damick

unread,
Oct 17, 2009, 11:05:02 PM10/17/09
to JSON-RPC
Yes i agree with you, this whole thread has gone down in a pretty bad
direction. We shouldn't be slamming the door on anyone.
Hopefully you will stay.





On Oct 11, 6:34 pm, esavard <savard.etie...@gmail.com> wrote:
> Hi,
>
> I'm new to the list and I must admit that I'm not impress by Lorenzo's
> response to Sin-young...
>
> Wow... This is definitely not the kind of (impolite) attitude I expect
> from any active member of any Open Source community!
>
> May be a more friendly approach could have been to point out that
> there is already other implementations of JSON-RPC for Ruby out there
> like:http://orbjson.rubyforge.org/and invite the poor guy to join
Reply all
Reply to author
Forward
0 new messages