-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Serialize smalldata to a blob-less entry in CGDFG #509
Comments
Entry
as wrapper?Smalldata
, how about using Blob
-less Entry
wrapper?
Not a bad idea, I'm about to separate out the big data as separate nodes though, so that may make this difficult. |
I guess we could still do it, we would just have to collect the entries around the node, but it would be a bit more difficult than a JSON blob inside the actual node. |
It fits in with why I originally created the struct TagData <: AbstractDataEntry
key::Symbol
family::String
tagids::Vector{Int}
bTt
end The problem was a concern that the payload could get too big. That's why the in-memory data store was created. I don't like and never used struct SmallData <: AbstractDataEntry
key::Symbol
data::String
#OR
smallDataDict::Dict{String, String}
end I guess |
Affects JuliaRobotics/Caesar.jl#514 |
Smalldata
, how about using Blob
-less Entry
wrapper?
we could if we really wanted to store something like this using a combo of the |
Also, julia> UUID("00000000-0000-0000-0000-000000000000")
UUID("00000000-0000-0000-0000-000000000000") |
Quirky decision, how about dropping the separate smalldata container, and only maintaining the
Data
plumbing but allow entries that do not have an associatedBlob
? We can flag theEntry
object as either having aBlob
or not (as immutable field in anentry
)?We can use the
Entry.description::String
field to store a JSONed string that represents theSmalldata
interface, and limit its size...Smalldata
functions are then fuss-free wrappers aroundentries
without worrying about what data types,MIME
,Entry
orBlob
.(bit like Macklemore, bought a broken keyboard): I have a short string, please store the short string...
cc @GearsAD @Affie
Related #403
The text was updated successfully, but these errors were encountered: