/ doc / tocNamespace / ARCCore / PropertyStreamLine / __TOCDet / Attribute / LongDescription

LongDescription

Edit keys at this level only

= FAQ: Is the property stream (and AgoRapide in general) strongly or weakly typed?0x000D0x000AThat is up to you.0x000D0x000AFor getting started, and just in order to experiment with some various data, you can start weakly typed, or just use strings everywhere.0x000D0x000AA standard storage like -PRich- and a generic -ARAAPI- built on top of that is not dependent on any pre-defined structure, it just accepts whatever is in the property stream.0x000D0x000AIn your C# code you can use multi-level indexing like this: 'DataStorage0x005B"Customer"0x005D0x005B"42"0x005D0x005B"FirstName"0x005D = "John"' without bothering about types at all (or just send the corresponding -PropertyStreamLine- 'dt/Customer/42/FirstName = John' to -TryParse-).0x000D0x000AAs your project matures and you see which classes and properties are more important, you can create the corresponding 'entity' classes and their -PropertyKeyEnum-, and specify more exact types for the properties.0x000D0x000ATaken into account concepts like -LinkInsertionInDocumentation- this will also constitute documenting your application.0x000D0x000ANote that though you can choose the level of dynamic typing (as shown), static strong typing is always a bit weaker with -PropertyAccess-. See -AssertTypeIntegrity- and -BoilerplateCodeProperties- for attempts at alleviating this.0x000D0x000A0x000D0x000AFAQ: How does the property stream format compare to the JSON format?0x000D0x000AThe short answer is that JSON is well suited when you want to transfer a whole object.0x000D0x000AIf you want to transfer parts of an object, for instance updating one single property, then the property stream format is better suited.0x000D0x000AA JSON representation of some given data points could be seen as a 'compiled' variant of the same data points stored as property stream lines.0x000D0x000AThis is because the original property stream lines for a given JSON representation may be spread out (not being located close to each other).0x000D0x000ANote however that if the actual property stream lines (for some given data points) reside consequently to each other in the data storage, then JSON would be a much more effective format for representation because it is much less verbose.0x000D0x000ATODO: Insert examples here in order to clarify.0x000D0x000A0x000D0x000ASome notes about compression:0x000D0x000ANote how the format used is somewhat verbose but well suited for on-disk compression.0x000D0x000AIt is for instance inefficient (storage-wise) to repeat the same context line after line.0x000D0x000ABut on the other hand, the underlying OS can easily be instructed to compress the storage files instead (something it should be able to do quite efficiently, leaving the size-issue to mostly constitute a network bandwidth problem.0x000D0x000ANote that some optimizations are performed anyway, see for instance -Timestamp- which describes how timestamps are not added to each and every property stream line but inserted as needed.0x000D0x000A0x000D0x000A

Edit keys at all sub levels.
NOTE: Edits are always additive. Use 'Invalid' in order to delete keys.

Generated 2025-08-02 17:05:15.308 UTC