0
Completed

Client Connector

Anonymous 2 years ago in Studio / Toolbox • updated by Gandalf 2 years ago 4
I read that you use SignalR for communication between the server and studio. Are there any plans on using SignalR to create a Client Connector+Source Tool so that we can push content to or message connected client apps?

>Garrett
tool studio
Under review
Hmmm... That's an interesting idea. Never really thought of that. What kind use case are you thinking of? At present you can connect to another Warewolf server and push content to that server in that way but are you thinking more of pushing content to the clients that are connected to a Warewolf Server?

Would love to hear what kind of application/use case you have in mind. Definitely something we can consider.

Thanks
I admit I'm still a beginner to this kind of stuff so forgive me if I word something that doesn't make sense but I was thinking of cases where you might have two or more client apps connected and maybe some data is updated by one of them and you want that immediately reflected in other apps. I was first thinking in terms of event listeners also but when I read about SignalR it sounded like something that could be used to accomplish this. Of course client apps could mimic this behavior by continually fetching data from a database but that's not true real time updates and is an unnecessary drain on resources.

Imagine some type of service related business that has two different client end apps, the sales department might have an app for entering a new order, and a dispatch department might have an app to assign a subcontractor to the order. When a new order entry is completed there should be an event that pushes an alert to the dispatch app notifying them of a new order in their queue.
The main thing I'm thinking of is real time updates and alerts to client apps, just like how the Warewolf server is able to give that kind of feedback to the studio.
Hi Garrett,

There are a few mechanisms that you can use right now to accomplish what you want to without having to add an extra layer of complexity to Warewolf. We are currently looking at extending the ESB to include queues that will provide that functionality.

But right now in Warewolf, you can schedule microservices to run at any given interval, so you can currently use this for pushing or notifications.

The other mechanism that is available, if you want something immediate, is to use Warewolf for web hooks - either fired by Warewolf, or an external process firing a Warewolf microservice as a web hook (simply calling the URL). Both of these techniques can be used as event mechanisms.

There are cases that I have seen, where record inserts within SQL server fire a SQL trigger that in turn fires a Warewolf microservice as a web-hook.