In that way, the client can create a regexp that defines its interest and simplify your flow without needing to:
Fetch the metainfo first.
Unmarshall the response.
Match the right file path.
This can be useful for the context of video media which usually only one video file is shared per magnet. Sample of a generic regexp that match the most popular video formats: \.(avi|mp4|mkv|webm)$.
Caveat:
Following the example, maybe a magnet points to many 'mp4's files, in that case, to maintain an easy algorithm correctness I suggest to return the first match.
Wildcard alternative:
Despite my last example, regex syntax can be really creepy, I prefer the unix shell wildcard notation that is:
The only way to select a specific file is by its path, example:
Using regexp it can happen like that:
In that way, the client can create a regexp that defines its interest and simplify your flow without needing to:
This can be useful for the context of video media which usually only one video file is shared per magnet. Sample of a generic regexp that match the most popular video formats:
\.(avi|mp4|mkv|webm)$
.Caveat: Following the example, maybe a magnet points to many 'mp4's files, in that case, to maintain an easy algorithm correctness I suggest to return the first match.
Wildcard alternative:
Despite my last example, regex syntax can be really creepy, I prefer the unix shell wildcard notation that is:
But I don't think that Golang provides a built-in support to this.