Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Talk:COSMOS Design 193420
We might be missing some context here. We jump right into the first 10 entries talking about key sets etc... If this is "the most simple example", and I have to know all this stuff about key sets, do we need to spend some time simplifying what we are doing?
What will the demo do? How will we show a collection assembly and a query assembly with no additional prerequisites? The last time we discussed this, I was thinking we'd have something like the following:
- Everything runs in the same eclipse environment. This was because we might want to tell people where to put break points in the code.
- We would have a singleton that held a collection of random values or even just a random value.
- We would have a data collection assembly that went off and added a new value to the collection or updated the one that was already there.
At this point, what you could do is show a simple client that did the control of the data collection assembly. This would be based on Joel's simple client that's there already. Start/stop is all we need here. Once that was done, you would have a query assembly that went off and got the values from the singleton.
If we wanted to, we could then take the simple example and have the information written to a database, e.g. derby. This would be a single table with a string value. It would show how all we need to do is drop in a new piece of the collection and query assemblies, not re-invent everything else. We could even do an XML document data store as well if we wanted.
In my head, this is where the simple demo stopped. It gives us plenty to get into and should be able to cover everything you've outlined in the previous page.