On 01/20/2016 04:57 PM, Peter S. Shenkin wrote: > On Wed, Jan 20, 2016 at 5:33 PM, Dimitri Maziuk <[email protected]> > wrote:
>> JSON encodes a single string. That is a problem for sending larger files >> over the net, say, an NMR structure of a larger molecule with 100 models >> in the file. >> > > That's not a problem, conceptually, because you can have an array of > structures. No, my point was that streaming isn't a part of JSON specification and common implementations do not offer it. https://en.wikipedia.org/wiki/JSON_Streaming You can cut one model out of a PDB file (or one structure out of and SDF) and the result is a valid file. In ASN.1 the length of the value is at the front. If you define your array as sequence, a single structure pulled out of the middle should be OK, but the entire sequence is invalid until you read it to the end. I think in practice you wouldn't define your array as a sequence and instead have a file full of "disjoint" single structures, possibly with some kind of metadata header. (I haven't touched ASN.1 since school, so don't quote me on this.) Oh wait, that sounds exactly like PDB with its REMARKs and MODELs. -- Dimitri Maziuk Programmer/sysadmin BioMagResBank, UW-Madison -- http://www.bmrb.wisc.edu
signature.asc
Description: OpenPGP digital signature
------------------------------------------------------------------------------ Site24x7 APM Insight: Get Deep Visibility into Application Performance APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month Monitor end-to-end web transactions and take corrective actions now Troubleshoot faster and improve end-user experience. Signup Now! http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140
_______________________________________________ Rdkit-discuss mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/rdkit-discuss
