Issue 693 in moose-technology: JSON import / export for Moose

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

Issue 693 in moose-technology: JSON import / export for Moose

moose-technology
Status: New
Owner: ----
Labels: Type-Enhancement Priority-Medium Component-Fame

New issue 693 by [hidden email]: JSON import / export for Moose
http://code.google.com/p/moose-technology/issues/detail?id=693

Due to the increase of JSON usage, we should provide a JSON alternative to  
the MSE file format.

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: Issue 693 in moose-technology: JSON import / export for Moose

moose-technology

Comment #2 on issue 693 by [hidden email]: JSON import / export for  
Moose
http://code.google.com/p/moose-technology/issues/detail?id=693

No concrete scenario. But, we have JSON support (Lukas implemented one on  
top of PetitParser even) and there are plenty of other systems that know  
how to consume and produce one.

I just think that it would be nice selling point to say that we can  
serialize in JSON.

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: Issue 693 in moose-technology: JSON import / export for Moose

moose-technology

Comment #3 on issue 693 by [hidden email]: JSON import / export for  
Moose
http://code.google.com/p/moose-technology/issues/detail?id=693

ok in that case we should use the msgstomp serializer too

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev