Skip to content
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

Add complex inline structures to the viwi protocol #59

Open
wzr1337 opened this issue Sep 11, 2017 · 3 comments
Open

Add complex inline structures to the viwi protocol #59

wzr1337 opened this issue Sep 11, 2017 · 3 comments

Comments

@wzr1337
Copy link
Contributor

wzr1337 commented Sep 11, 2017

For some use cases it might be needed to allow complex data structures in addition to primitives

(see automotive-bg/rsi/protocol/)

@anawhj
Copy link
Member

anawhj commented Sep 27, 2017

In the RSI protocol document, author specifies the graph interface where all leaf nodes seems to have a primitive value (int, string, etc.). I wonder the primitives you mentioned is same as the primitive value for the leaf nodes I mentioned.

In general, the leaf nodes could have a value as a nested object within a JSON format while I guess you want to make the leaf nodes have a value like a inline string with complex structure. Am I right? I'd like to see a use case to understand why the complex data structures with inline need.

@wzr1337
Copy link
Contributor Author

wzr1337 commented Nov 6, 2017

@anawhj You are partially right. I want to nest complex JSON structures in leaf node properties.

E.g. PlayerObject:

{
  "id": "01065B9A-6908-48E0-9D2E-914160480826",
  "name": "Player One",
  "uri": "/media/players/01065B9A-6908-48E0-9D2E-914160480826",
  "offset": 1234,
  "artist": {
    "name": "P!nk",
    "birthday": {
      "month": 9,
      "day": 8,
      "year": 1979
    }
  }
}

In this example, I want to group the artist name with additional information. The birthday is again a substructure.

I still want to handle the complex sturcture as "like primitive", as you will not be able to access birthday or name directly, nor filter nor any other complex operation. It would just be a well structured "BLOB" of data, Events will fire when it changes.. regardless of changes in "name" or "birthday".

I will publish a concrete Pull-Request before Thursday this week.

@wzr1337
Copy link
Contributor Author

wzr1337 commented Nov 7, 2017

Just opened the PR referenced above:
#67

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants