Github user jantzeca commented on the issue:
https://github.com/apache/tinkerpop/pull/928
@spmallette Okay, thank you!
---
Github user spmallette commented on the issue:
https://github.com/apache/tinkerpop/pull/928
@jantzeca this merged a day or so ago. it has not been released yet to
nuget. we have releases scheduled for 3.2.10 and 3.3.4 in the next couple of
weeks. it will be available then.
---
Github user jantzeca commented on the issue:
https://github.com/apache/tinkerpop/pull/928
My latest Gremlin.net NuGet package is showing as 3.3.3. Is the package for
these new changes not ready yet?
---
Github user FlorianHockmann commented on the issue:
https://github.com/apache/tinkerpop/pull/928
@deejvince: Did you see [the integration
test](https://github.com/apache/tinkerpop/blob/master/gremlin-dotnet/test/Gremlin.Net.IntegrationTest/Driver/GremlinClientTests.cs#L233)
added with
Github user deejvince commented on the issue:
https://github.com/apache/tinkerpop/pull/928
@FlorianHockmann
Could you please post a working example on how to use the delegate with the
driver connection with GremlinClient?
---
Github user Pede23 commented on the issue:
https://github.com/apache/tinkerpop/pull/928
I need this merged so I add authentication headers to my gremlin requests!
I'm sure this will be extremely useful to anyone else trying to encrypt their
connection with Amazon Neptune.
VOT
Github user dkuppitz commented on the issue:
https://github.com/apache/tinkerpop/pull/928
Hm, alright. I don't have an environment to test it myself, but apparently
I'm missing something; I thought it would be a simple property delegation.
VOTE +1
---
Github user FlorianHockmann commented on the issue:
https://github.com/apache/tinkerpop/pull/928
I also wanted to implement it like that as first, but unfortunately the
[`ClientWebSocket.Options`
property](https://docs.microsoft.com/dotnet/api/system.net.websockets.clientwebsocket.opt
Github user dkuppitz commented on the issue:
https://github.com/apache/tinkerpop/pull/928
IMO it would be better to expose the options as a property unless there's a
good reason to not allow any changes in options after the client has been
initialized. But since the underlying `Client
Github user FlorianHockmann commented on the issue:
https://github.com/apache/tinkerpop/pull/928
Yes, that should be possible. With this PR, you can provide a delegate to
configure the ClientWebSocketOptions which should also include custom headers.
---
Github user deejvince commented on the issue:
https://github.com/apache/tinkerpop/pull/928
@FlorianHockmann this PR should enable setting custom headers on the
WebSocket, right?
like:
Options.SetRequestHeader("Authorization", "Bearer " + token);
Thank you,
D
11 matches
Mail list logo
