Desktop apps and Web - what makes sense?

Alex Clay aclay at mac.com
Thu Aug 12 18:05:03 UTC 2021


Hi Greg,

I highly recommend using a standard for a RESTful JSON API. We use JSON:API: https://jsonapi.org <https://jsonapi.org/>

Just remember a REST API works in resources, not relational tables. It's a different model of thinking about data than a traditional RDBMS.

Alex 

> On Aug 12, 2021, at 13:59, Grzegorz (Greg) Pasternak <gpasternak at cogeco.ca> wrote:
> 
> Doug;
> 
> Great write up, though suspiciously close to what I am thinking ;-)
> 
> Speaking of JSON, how complex should it be allowed to be?  Particularly I am thinking about two or more layers of list elements within the list of elements.  Should this be allowed or avoided? How to manage element names? (data dictionary or schema classes column names?  what about calculated elements?)
> 
> Also, speaking of Omnis REST and user validation, how to go about user validation?  Should the credentials be encrypted and included in each request?
> 
>> but DO NOT (please do not) take that as a blanket statement to write everything in pgsql.    perhaps 0.5% of our code is in pgsql.   its just an option.
> 
> Now I feel much better knowing that.
> 
> Greg
> 
> 
> 
> 
>> On Aug 12, 2021, at 12:31 PM, Doug Easterbrook <doug at artsman.com> wrote:
>> 
>> hi Greg:
>> 
>> We developed our REST api a while back.  Then, when we ware Euromnis about 3/4 years ago, I sat in on Jason’s presentation on making rest api’s in omnis.
>> 
> 
> Right, I do remember.
> 
> 
> _____________________________________________________________
> Manage your list subscriptions at http://lists.omnis-dev.com
> Start a new message -> mailto:omnisdev-en at lists.omnis-dev.com 



More information about the omnisdev-en mailing list