HNeukermans
HNeukermans
Hi @DarkXaHTeP. Indeed. I know this is a very usefull feature. At the same time it is also the hardest to implement. I need to do some research on this...
Hi @c-robison, Seems like a valueable contribution. Can, I ask you why did you close the PR?
Yeah cool, if you can, just reopen it. I will take a look, at what parts I can use...
indeed @Him2021. Good feedback. I already proposed a similar idea in previous issues. [link](https://github.com/HNeukermans/adal-ts/pull/9) To retrieve the token or user y**ou only need to talk to the storage**. That's why...
To understand, the reasoning behind this api and why I came up with this: - `Authentication.getStorage().getIdToken()` we must enter a broader discussion. It is a discussion about making the behavior...
You'r welcome. Thx for the contributions so far.
you need to send the token as a query parameter instead of `qs:{userId:1}` write `qs:{userId:1, token: 'your token'}`
Hi @Usman235,, thx a ton. I didn't even know this existed inside signalr. Sorry, my fault... Seems like a next ng2-signalr super feature !! As a workaround inside your typescript...
I think you need to pass in IConnectionOptions to the connect method. something like Signalr.connect({ qs: {blabla : 'fff' }}); But this has the drawback of creating a new connection....
Dear @MikePerilli, are you pushing messages to the client every 2 seconds ? Remember ng2-signalr is simply a wrapper around signalr. This means that calling connect does actually invoke signalr.connect()...