You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
So right now we are doing the verification in the spooler. However, the config dictionary that the user obtains from qlue is not nowing anything about the spooler. We somehow have to connect them. I see two main routes:
Move the verification entirely into qlue. The spooler could then get some API access to qlue to verify that everything is in sync.
The spooler is handling most of it as is right now. This gives an enormous amount of power to the back-end and could be very practical.
Here, are a few things that we should think about:
The communication of the spooler and qlue might happen through an API.
The front-end has to communicate the information to the user.
All the spoolers should decide how the communicate with the qlue, but it seems fairly open.
So right now we are doing the verification in the spooler. However, the config dictionary that the user obtains from
qlue
is not nowing anything about the spooler. We somehow have to connect them. I see two main routes:qlue
. The spooler could then get some API access toqlue
to verify that everything is in sync.Here, are a few things that we should think about:
spooler
andqlue
might happen through an API.qlue
, but it seems fairly open.@RohitPrasadBhatt what do you think ?
The text was updated successfully, but these errors were encountered: