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
Currently typescript ogmios client is using host and port of the ogmios instance. But we can't always provide these information of the omgios instance. For example if we want to use a node provider instead of a local ogmios configuration, all we have is a url for https and wss connection. I also tested the correct behavior of ogmios client with the described URLs by patching the createConnectionObject function and with some simple modification it can support the instance url.
Why is it a good idea?
To broaden the ogmios client usecases
What is the current alternative and why is it not good enough?
Now its supporting host and port and it works fine but it cant support all connection types.
The text was updated successfully, but these errors were encountered:
What is your idea? Provide a use case.
Currently typescript ogmios client is using host and port of the ogmios instance. But we can't always provide these information of the omgios instance. For example if we want to use a node provider instead of a local ogmios configuration, all we have is a url for https and wss connection. I also tested the correct behavior of ogmios client with the described URLs by patching the
createConnectionObject
function and with some simple modification it can support the instance url.Why is it a good idea?
To broaden the ogmios client usecases
What is the current alternative and why is it not good enough?
Now its supporting host and port and it works fine but it cant support all connection types.
The text was updated successfully, but these errors were encountered: