Paw-Issues icon indicating copy to clipboard operation
Paw-Issues copied to clipboard

Websocket support

Open joshhopkins opened this issue 5 years ago • 18 comments

Any plans on websocket support?

joshhopkins avatar Mar 12 '19 14:03 joshhopkins

and graphql subscriptions as well (based on websocket)

ghost avatar Mar 26 '19 10:03 ghost

Yeah I'd definitely use websocket and graphql support, most of our API's are on Lambda and we use web sockets quite a bit with mobile apps.

marcfielding1 avatar Apr 29 '19 12:04 marcfielding1

Was this ever introduced? I found an comment from May '17 saying that it might be on the way so just wanted to check... thanks!

joeczucha avatar Feb 07 '20 14:02 joeczucha

Any news on websocket support?

jk avatar Oct 05 '20 13:10 jk

+1

kazhuravlev avatar Nov 26 '20 10:11 kazhuravlev

Meanwhile use: https://websocketking.com

(for people like me who needed to do a quick websocket test and noticed Paw didn't support it)

navaru avatar Dec 30 '20 18:12 navaru

Not inside Paw either but at least sponsored by Paw https://hoppscotch.io 🤷‍♂️

KuhlTime avatar Jan 04 '21 16:01 KuhlTime

Err, you do realize that there are people asking a question here that BUY a Paw license and would hope for some kind of response?

marcfielding1 avatar Jan 07 '21 22:01 marcfielding1

any updates?

vec715 avatar Oct 27 '21 09:10 vec715

I'm curious if there's been any traction on this?

blevasseur-godaddy avatar Nov 15 '21 18:11 blevasseur-godaddy

use Postman, I removed my subscription for PAW because I'm not paying for a product that is quite clearly not supported properly - PAW WAS awesome in my book, but it's not the winner - also this is not a complicated feature, I don't quite understand why it's hard work engaging on it.

I mean common this was nearly a year ago?!

marcfielding1 avatar Nov 15 '21 23:11 marcfielding1

It should be noted that this repo is being closed and there is a link on Readme for raising tickets though, so it might better to migrate our requests to here as this repo might not even be observed any more. Here is the link from the readme.

https://paw.cloud/support?app=com.luckymarmot.Paw

marcfielding1 avatar Nov 15 '21 23:11 marcfielding1

It should be noted that this repo is being closed and there is a link on Readme for raising tickets though, so it might better to migrate our requests to here as this repo might not even be observed any more. Here is the link from the readme.

https://paw.cloud/support?app=com.luckymarmot.Paw

That's not an excuse for the team not addressing the request and the many votes casted on it. I think giving an official statement on how existing issues will be handled before closing and abandoning the repo is the appropriate action.

alobaili avatar Nov 16 '21 00:11 alobaili

Whilst I do agree, during transition periods between orgs, things can get lost, now being annoyed is not going to change the facts, finding a solution will.

marcfielding1 avatar Nov 16 '21 01:11 marcfielding1

We can troll this thread all year, not gonna make a difference, being angry only really changes your life - whilst we're entitled to feel aggrieved I don't believe the software owners want to lose subscribers, I believe they made a mistake, as have we all, so let's figure this out.

marcfielding1 avatar Nov 16 '21 01:11 marcfielding1

To be blunt, if we could make this ourselves we wouldn't be here, so you have two choices, don't be here. Or engage. I think I'll select engage given I hadn't noticed the change of ownership.

marcfielding1 avatar Nov 16 '21 01:11 marcfielding1

This would be a cool feature to include with Paw. 😊

eivindml avatar Oct 26 '22 12:10 eivindml

Had the pro version so far, apparently which isn't required anymore. Web socket not yet present. Switching to Firecamp for good

aiank avatar Dec 16 '22 14:12 aiank