- You'd also need to map null to something in classads. - ClassAds would still be a superset of JSON. - There would be natural guidance for a binary encoding of ClassAds. - You could probably update the ClassAds language to have multiple representations - classical new ClassAds, JSON ClassAds, binary ClassAds, and XML ClassAds. As all would use a different first character, you could have a single parser/lexer for all representations.
What's the benefit though - versus just having different converters written in C++?
Brian
If we flipped the meaning of '[]' and '{}' in ClassAds, and allowed colons as an assignment operator*, and maybe checked the different string escapes, would every JSON object automatically be a ClassAd?
It'd be kind of slick if ClassAds and JSON were a little more interoperable, and we could get some cool stuff somewhat for free.
We could go a little farther, and work out a full syntax for ClassAds in JSON, maybe by looking at some of the JSON Referencing ideas:
This could all be first-steps towards easier interactions with HTCondor in other languages and environments.
-Erik
*which I swore I thought Ye Olde ClassAds could do, but maybe it was just the config files
_______________________________________________
HTCondor-devel mailing list
HTCondor-devel@xxxxxxxxxxx
https://lists.cs.wisc.edu/mailman/listinfo/htcondor-devel
|
![[Computer Systems Lab]](http://www.cs.wisc.edu/pics/csl_logo.gif){kind=logo}