On Sun, 11 Aug 2019, Joost van der Sluis wrote:
Op 10-08-19 om 18:37 schreef Michael Van Canneyt:
On Sat, 10 Aug 2019, Marco van de Voort wrote:
Op 2019-08-10 om 17:30 schreef Joost van der Sluis:
And who else wanna help?
Why not simply port superobject?
2 reasons:
1. Interface based. Really bad idea.
There can be a really good use for interfaces regarding streaming. Like
you saw earlier in the fppkg-repository code.
I think the only case when interfaces are truly needed is in IPC/RPC.
For the rest it just complicates otherwise simple things.
I will use them when useful, which I think is far less than commonly assumed.
As such I'm violently opposed to the 'you must always program an interface'
attitude.
2. JSON only.
3. I didn't really know it.
You don't miss out on that. It's better than the mess Embarcadero produced,
but still needlessly complicated IMHO.
And if you need more reasons: the jsonrtti has just this. I still need
to add some functionality to it from the restbase unit (dynamic
arrays) but other than that I've been using it since ages.
I use jsonrtti now, and with some additions it works like I want. But
the goal is somewhat more generic, yes.
I understood that, I just compared it to superobject, not to your eventual
goal.
What additions are you talking about ? Can we incorporate it ? Improvements are
always welcome.
Note that the SQLDB rest bridge has dataset result streaming in various formats.
It's somewhat similar to your goal, but is limited to datasets.
Michael.
_______________________________________________
fpc-pascal maillist - fpc-pascal@lists.freepascal.org
https://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal
