combination of signalr with webapi
simple table of big datasets with push updates through signalr, but data transfer via webapi or other rest calls. the sample could show a way to get a good integration of the two technologies.
Could you clarify what you mean by big datasets? What does the sample show? I can more see, exposing a rest api that also does push.
the data is irrelevant for the sample, could be something from small json data of a couple of business objects up to a binary blob of an file. the payload of an signalr message should not be too big. sometimes you have to combine signalr well with other technologies.
for example: lets say we have a typical business application with tables and forms. one column of the dataset is the state of an workflow. updating only this text with information from the signalr message is a good idea. but if more data changes, the message should only inform the client to get all the new data of the business object via an webapi call.
Lets get concrete here. Describe a specific example. I'm still confused as to what you want to see.
- list of contacts (firstname, lastname, age, state)
- create form of contact (save -> no signalr message, upload via webapi)
- save on server pushes notification to all other clients
- all client check for push from server and refresh data via webapi call (not the sender client)
- a minute later on the server the state from "in progress", changes to "checked" (a workflow in real world)
- all clients again update there data because of an signalr message from the server
Awesome, about number 5. What does that mean? What state changes from inprogress to checked? How does that relate to the contact list?
in real world projects this could be something like a order information, seat reservation, shipping information, credit-card check...
let's make it a seat reservation - it's delay is caused by an human approval workflow.
I get that you're trying to simulate a real world scenario, but I just want specifics. Someone has to code this up so it needs to be 100% unambiguous.
i think a seat reservation for people including a human approval through a simple c# console appliation is ok. the technical implementation should not send the data as payload in the signalr message, but force the relevant clients to load the data via webapi.
this pattern can later be used in other real world applications as starting point.