Declined
Last Updated: 22 Nov 2021 13:54 by ADMIN
Jason
Created on: 03 Dec 2014 01:40
Category: Data Source
Type: Feature Request
1
Client Side Data Bus (ok I made this up I admit it) Universal DataSource
A single managed Ajax / Socket connection (can set for Ajax or Sockets or have it fall back) that you can pass a model to on the client and a command CRUD (Get, Post, Put, Delete) and an ASP.NET WEB API implementation on server side in Web API / Socket.

The issue I encounter with DataSources is that you have to set up a connection test it and for every one its more work and testing and possibility of error  in the app. I just want a client side connection to Sockets or Web API that I can tell to save something and have to set up and configure this connection once in JS and onece in C#

If you pass the Universal Data Source Data Bus a Model a Command (Get, Post, Put, Delete) and a Name / Path for the Model it hits a universal service that processes this it generates a predictable Web API call pattern that Web API can easily be set up to (Controllers to meet) or one big controller
2 comments
Grahame
Posted on: 24 Nov 2017 16:28
IMHO I'd go the other way breaking the services down into smaller API calls; the micro services approach can give better scalability and performance with the routing of requests via a load balancer so as far as the client code is concerned the URI endpoint is consistent and a signal point of connection; however in real terms not ;)   
Jason
Posted on: 03 Dec 2014 01:42
This also means the pipeline could be easily persisted client side since there is one connection optionally synced by some cmnd or time interval