Minor documentation improvements
I got some feedback from Redditors, and addd some information as to what a magnet url is, and why a magnet-url parser is useful
This commit is contained in:
parent
95f912f950
commit
e452658bc8
23
README.md
23
README.md
|
@ -1,7 +1,26 @@
|
||||||
[![Build Status](https://www.travis-ci.com/billyb2/parse-magnet-rs.svg?branch=main)](https://www.travis-ci.com/billyb2/parse-magnet-rs)
|
[![Build Status](https://www.travis-ci.com/billyb2/parse-magnet-rs.svg?branch=main)](https://www.travis-ci.com/billyb2/parse-magnet-rs)
|
||||||
# The Rust Magnet URL Parser!
|
# The Rust Magnet URL Parser!
|
||||||
# Intro
|
# What is a magnet url
|
||||||
magnet_url-rs has the goal of, as you may have guessed, parsing the parts of magnets. It does
|
A magnet is a URI scheme that identifies files by their hash,
|
||||||
|
normally used in peer to peer file sharing networks (like
|
||||||
|
Bittorrent). Basically, a magnet link identifies a torrent you
|
||||||
|
want to download, and tells the torrent client how to download
|
||||||
|
it. They make it very easy to share files over the internet,
|
||||||
|
and use a combination of DHT and trackers to tell your torrent
|
||||||
|
client where other peers who can share the file with you are.
|
||||||
|
|
||||||
|
# Why is magnet_url
|
||||||
|
While working on a side project, I realized that I had the
|
||||||
|
misfortune of trying to get the component parts of a magnet-url
|
||||||
|
and then do further processing of them. I quickly wrote some
|
||||||
|
Regex for it, but then I realized that this would be really
|
||||||
|
useful for other projects that are dealing with torrents in
|
||||||
|
Rust. By making it modifiable, too, it would allow for the
|
||||||
|
creation of custom magnet links, which would also be useful for
|
||||||
|
torrent based projects.
|
||||||
|
|
||||||
|
# Why use magnet_url
|
||||||
|
magnet_url has the goal of, as you may have guessed, parsing the parts of magnets. It does
|
||||||
this using some relatively simple regexes. The crate is designed to be very simple and efficient,
|
this using some relatively simple regexes. The crate is designed to be very simple and efficient,
|
||||||
with a lot of flexibility. It's also designed to be relatively easy to handle errors, and
|
with a lot of flexibility. It's also designed to be relatively easy to handle errors, and
|
||||||
modification of it's source is greatly encouraged through documentation and it's license.
|
modification of it's source is greatly encouraged through documentation and it's license.
|
||||||
|
|
22
src/lib.rs
22
src/lib.rs
|
@ -14,8 +14,26 @@ const WEB_SEED_RE_STR: &str = r"ws=([A-Za-z0-9!@#$%^:*<>,?/()_+=.{}\{}\-]*)(&|$|
|
||||||
const ACCEPTABLE_SOURCE_RE_STR: &str = r"as=((\w+)[A-Za-z0-9!@#$%^:*<>,?/()_+=.{}\\-]*)(&|$|\s)";
|
const ACCEPTABLE_SOURCE_RE_STR: &str = r"as=((\w+)[A-Za-z0-9!@#$%^:*<>,?/()_+=.{}\\-]*)(&|$|\s)";
|
||||||
const MANIFEST_TOPIC_RE_STR: &str = r"mt=((\w+)[A-Za-z0-9!@#$%^:*<>,?/()_+=.{}\\-]*|urn:(sha1|btih|ed2k|aich|kzhash|md5|tree:tiger):([A-Fa-f0-9]+|[A-Za-z2-7]+))(&|$|\s)";
|
const MANIFEST_TOPIC_RE_STR: &str = r"mt=((\w+)[A-Za-z0-9!@#$%^:*<>,?/()_+=.{}\\-]*|urn:(sha1|btih|ed2k|aich|kzhash|md5|tree:tiger):([A-Fa-f0-9]+|[A-Za-z2-7]+))(&|$|\s)";
|
||||||
|
|
||||||
|
///# What is a magnet url
|
||||||
///# Intro
|
///A magnet is a URI scheme that identifies files by their hash,
|
||||||
|
/// normally used in peer to peer file sharing networks (like
|
||||||
|
/// Bittorrent). Basically, a magnet link identifies a torrent you
|
||||||
|
/// want to download, and tells the torrent client how to download
|
||||||
|
/// it. They make it very easy to share files over the internet,
|
||||||
|
/// and use a combination of DHT and trackers to tell your torrent
|
||||||
|
/// client where other peers who can share the file with you are.
|
||||||
|
///
|
||||||
|
///# Why is magnet_url
|
||||||
|
///While working on a side project, I realized that I had the
|
||||||
|
/// misfortune of trying to get the component parts of a magnet-url
|
||||||
|
/// and then do further processing of them. I quickly wrote some
|
||||||
|
/// Regex for it, but then I realized that this would be really
|
||||||
|
/// useful for other projects that are dealing with torrents in
|
||||||
|
/// Rust. By making it modifiable, too, it would allow for the
|
||||||
|
/// creation of custom magnet links, which would also be useful for
|
||||||
|
/// torrent based projects.
|
||||||
|
///
|
||||||
|
///# Why use magnet_url
|
||||||
/// magnet_url has the goal of, as you may have guessed, parsing the parts of magnets. It does
|
/// magnet_url has the goal of, as you may have guessed, parsing the parts of magnets. It does
|
||||||
/// this using some relatively simple regexes. The crate is designed to be very simple and efficient,
|
/// this using some relatively simple regexes. The crate is designed to be very simple and efficient,
|
||||||
/// with a lot of flexibility. It's also designed to be relatively easy to handle errors, and
|
/// with a lot of flexibility. It's also designed to be relatively easy to handle errors, and
|
||||||
|
|
Loading…
Reference in New Issue