search

postmanlabs / postman-app-support

Postman is an API platform for building and using APIs. Postman simplifies each step of the API lifecycle and streamlines collaboration so you can create better APIs—faster.
https://www.postman.com
5.85k stars 839 forks source link

Output data from long running HTTP connection / stream #278

Open dontstopnow opened 11 years ago

dontstopnow commented 11 years ago

When connecting to a streaming HTTP connection such as the twitter streaming api, no response is shown, but when connecting using curl the output is spooled out in the terminal. Any way to update the response window with the output? Thanks!

a85 commented 11 years ago

I doubt if this is possible using the way Postman pings API's right now. Can you give me a link to an example which works on the web?

a85 commented 11 years ago

Update: The new Chrome packaged apps platform has a chrome.socket module to send and receive data using TCP and UDP connections. Consuming any API should be possible within Postman. http://developer.chrome.com/apps/socket.html

sdnts commented 8 years ago

@dontstopnow Can you check if this is still an issue with the latest version of the app (v4.8)?

JimG777 commented 8 years ago

This is an issue for me, but I did not test twitter. Nest also has an HTTP Streaming API (https://developers.nest.com/documentation/cloud/rest-streaming-guide/). On testing with my own test server (via node.js), Postman 4.8.1 (Chrome/Windows) just says "Loading..." forever. Curl is okay, as long as each 'response' has a carriage return to terminate it. Only then does curl update. From a browser, one would usually add an accept header for "text/event-stream".

JohnPelletier commented 7 years ago

@a85, any sample implementation you can show of the chrome.socket integration with postman? Would really help.

mccannt commented 6 years ago

Putting my 2 cents in on this one as well.

We are currently trying to test in our company some streaming API's and running into the exact same issues. Works via cURL calls but Postman shows nothing and eventually will crash when the buffer fills up.

Can we get this added to the backlog and investigated?

I am running on Postman 6.0.10 on Mac. cc: @madebysid and @a85

shamasis commented 5 years ago

Showing a fully streamed response (HTTP2/Websocket/etc) is a different beast than the issue of choking on large responses. Additionally, postman does support receiving streamed responses... it just does not have a way to stream it to the UI and because it loads at one chunk, it causes buffer overflow.

What @mccannt mentioned at https://github.com/postmanlabs/postman-app-support/issues/278#issuecomment-389572117 is something that should work. We have covered some basics for the same in our latest Canary build and would release a variant that does not choke on buffer overflow very soon.