I was writting some extra tests for the python rest client and
checking what are the types allowed.
The boolean, strings, integers and floats seem to be OK when the
client receives the JSOn from the server. But if I serialize a date or
datetime, I have no way to know whether I must do a casting the
Hum...maybe we should have the type of object in the json string?
"data": {"name" : {"string" : "Max"}, "age": {"int" :31} }
also how about arrays? "string[]" : ["Max", "Javier","Peter"]
On Tue, Nov 23, 2010 at 1:02 PM, Javier de la Rosa wrote:
> I was writting some extra tests for the pytho
Javier, Max, good point!
Jim, what do you say about that? How type safe can we make the REST
API? At least I think this warrants an issue over at
https://trac.neo4j.org/ticket/286 for this.
Cheers,
/peter neubauer
GTalk: neubauer.peter
Skype peter.neubauer
Phone +46 704 106975
On Tue, Nov 23, 2010 at 16:05, Peter Neubauer
wrote:
> Jim, what do you say about that? How type safe can we make the REST
> API? At least I think this warrants an issue over at
> https://trac.neo4j.org/ticket/286 for this.
Thank you Peter and Max for the quick response. It would be great to
have
Hi folks,
My concern about this is that we're already taking liberties with the media
type application/json.
Adding this kind of annotation definitely takes us into very neo4j-specific
territory (which might be a good thing). I responded to the ticket, saying that
perhaps we should consider a
5 matches
Mail list logo