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
Ok, after porting one of my grpc clients to this sdk (or the simple alternative) there is one major design thing I'm concerned about.
It looks like I need different code paths for singularitynet and for calling the service without the singularitynet layer. e.g. if I have a local service, and I'm testing it (without any blockchain stuff), I want to use almost the exact same code as when I'm calling the production service.
Ideally I'd be able to fetch the model from either a local directory (yet to be published), or from snet. Then it'd be compiled and I could create a stub and request, but it'd only add the MPE stuff if I'm actually calling the service via MPE.
Any idea if you've already allowed for this @vforvalerio87 - or if it'd be easy to support something like this?
Ok, after porting one of my grpc clients to this sdk (or the simple alternative) there is one major design thing I'm concerned about.
It looks like I need different code paths for singularitynet and for calling the service without the singularitynet layer. e.g. if I have a local service, and I'm testing it (without any blockchain stuff), I want to use almost the exact same code as when I'm calling the production service.
Ideally I'd be able to fetch the model from either a local directory (yet to be published), or from snet. Then it'd be compiled and I could create a stub and request, but it'd only add the MPE stuff if I'm actually calling the service via MPE.
Any idea if you've already allowed for this @vforvalerio87 - or if it'd be easy to support something like this?
If a directory and endpoint is provided, then no MPE work is done, nothing is looked up on the registry etc.
Edit: updated to include what @astroseger's simple-sdk would have to look like.
Originally posted by @ferrouswheel in #5 (comment)
The text was updated successfully, but these errors were encountered: