sox-devel@lists.sourceforge.net unofficial mirror
 help / color / mirror / code / Atom feed
From: Jan Stary <hans@stare.cz>
To: sox-devel@lists.sourceforge.net
Subject: playing remote files
Date: Sat, 23 Feb 2013 16:29:16 +0100	[thread overview]
Message-ID: <20130223152916.GA17249@www.stare.cz> (raw)

Currently. sox uses wget(1) to access remote files and streams.
What is the developers' opinion about what do do with it
(if anything)?

The obvious candidates are wget(1), ftp(1), curl(1) and libcurl(3).
What would be the pros and cons of each?

http://sourceforge.net/tracker/?func=detail&aid=1713308&group_id=10706&atid=360706

(I am not sure if there are other entries in the tracker
related to this.)

	Jan


------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_feb

             reply	other threads:[~2013-02-23 15:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-23 15:29 Jan Stary [this message]
2013-02-26 16:14 ` playing remote files Chris Bagwell
2013-02-26 19:22   ` Eric Wong
2013-02-26 20:52     ` Jan Stary
2013-02-26 20:51   ` Jan Stary
2013-02-26 23:18     ` Eric Wong

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-list from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://lists.sourceforge.net/lists/listinfo/sox-devel

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20130223152916.GA17249@www.stare.cz \
    --to=sox-devel@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/sox.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).