bairav
How to handle(long running) chunked post request
We are developing ffmpeg processes monitor, in that , what is the best way to handle long running chunked post request.
from FFMPEG manpage:-
-progress url ( global )
Send program-friendly progress information to url.
Progress information is written approximately every second and at the end of the encoding process. It is made of “key=value” lines.
I captured HTTP request that ffmpeg performs for progress:
POST /progress.php HTTP/1.1
Transfer-Encoding: chunked
User-Agent: Lavf54.29.104
Accept: /
Connection: close
Host: localhost
8f
frame=91
fps=0.0
stream_0_0_q=23.0
total_size=205437
out_time_ms=4388571
out_time=00:00:04.388571
dup_frames=1
drop_frames=0
progress=continue
92
frame=210
fps=209.5
stream_0_0_q=11.0
total_size=569264
out_time_ms=9357642
out_time=00:00:09.357642
dup_frames=1
drop_frames=0
progress=continue
92
frame=368
fps=244.8
stream_0_0_q=4.0
total_size=814739
out_time_ms=15952109
out_time=00:00:15.952109
dup_frames=1
drop_frames=0
progress=continue
94
frame=440
fps=219.0
stream_0_0_q=10.0
total_size=1921815
out_time_ms=18924263
out_time=00:00:18.924263
dup_frames=1
drop_frames=0
progress=continue
Popular in Questions
Other popular topics
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #deployment
- #library
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #channels
- #elixirconf
- #exunit
- #discussion
- #code-sync
- #javascript
- #podcasts
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixir-ls
- #phoenix_html
- #iex
- #blog-post
- #graphql
- #genstage
- #ai
- #websockets
- #supervisor
- #advent-of-code
- #elixirconf-us
- #distillery
- #processes
- #forms
- #api
- #metaprogramming
- #security
- #performance









