issues
search
felipemoraes
/
warc-tools
Automatically exported from code.google.com/p/warc-tools
0
stars
0
forks
source link
issues
Newest
Newest
Most commented
Recently updated
Oldest
Least commented
Least recently updated
SRS 52 — Extensions to "HTTrack", "wget" and "curl" incorporating libwarc shall be provided as patches to recent and specific versions of each tool...
#58
GoogleCodeExporter
closed
9 years ago
1
SRS 51 — Python scripts shall be implemented incorporating libwarc, and making all of the functionality of libwarc and API available in Python.
#57
GoogleCodeExporter
closed
9 years ago
1
SRS 50 — The command line tools and API in SRS 50 will not include any links extraction features
#56
GoogleCodeExporter
closed
9 years ago
1
SRS 49 — A set of command line tools and an API incorporating libwarc shall enable the collection of online documents, such as html and embedded files, etc., and write them to valid WARC- records
#55
GoogleCodeExporter
closed
9 years ago
1
SRS 48 — A set of command line tools incorporating libwarc shall perform migration of "curl" archives to WARC-records.
#54
GoogleCodeExporter
closed
9 years ago
1
SRS 47 — A set of command line tools incorporating libwarc shall perform migration of "wget" archives to WARC-records.
#53
GoogleCodeExporter
closed
9 years ago
1
SRS 46 — The HTTrack archive file format and link strategy may vary from version to version of HTTrack...
#52
GoogleCodeExporter
closed
9 years ago
1
SRS 45 — A set of command line tools incorporating libwarc shall perform migration of "HTTrack" archives to WARC-records.
#51
GoogleCodeExporter
closed
9 years ago
1
SRS 44 — It shall be possible to specify non-default operations of "arc2warc" using a named configuration file, which will describe the desired ARC-record to WARC-record conversion.
#50
GoogleCodeExporter
closed
9 years ago
2
SRS 43 — "arc2warc" shall have make a default operation in cases where an ARC-record has no corresponding field in the WARC-record.
#49
GoogleCodeExporter
opened
9 years ago
2
SRS 42 — The default operation of "arc2warc" shall carry out a one-to-one mapping of record fields...
#48
GoogleCodeExporter
closed
9 years ago
1
SRS 41 — A command line tool “arc2warc” incorporating libwarc shall be able to migrate data in ARC-records to WARC-record format.
#47
GoogleCodeExporter
closed
9 years ago
1
SRS 40 — Libwarc shall be incorporated within a Lighttp module to enable all actions specified in SRS 34-36 to be executed within lighttp.
#46
GoogleCodeExporter
closed
9 years ago
1
SRS 37 — WARC Browser shall support a client-side rewriting interface by using javascript code to rewrite links ...
#45
GoogleCodeExporter
closed
9 years ago
5
SRS 39 — Libwarc shall be incorporated within an Apache module to enable all actions specified in SRS 34-36 to be executed within Apache
#44
GoogleCodeExporter
closed
9 years ago
1
SRS 38 —A web proxy interface shall be implemented that allows the user to set their web browser proxy to the one provided by the interface...
#43
GoogleCodeExporter
opened
9 years ago
3
SRS 36 — WARC browser shall not support CDX files because the CDX file format is not a standard at this time and is outside of scope
#42
GoogleCodeExporter
closed
9 years ago
2
SRS 35 — For security reasons, it shall not be possible to perform write or update operations on a WARC-record remotely
#41
GoogleCodeExporter
closed
9 years ago
1
SRS 34 — It shall be possible to perform read operations (read from offset, filters, etc.) on WARC-records from a remote location via http.
#40
GoogleCodeExporter
closed
9 years ago
1
SRS 33 — Libwarc shall provide a set of classes to enable remote management of WARC-records
#39
GoogleCodeExporter
closed
9 years ago
2
SRS 32 — The command line tool shall notify the user of any WARC-record's anomalies, missing required fields or incompatible fields types.
#38
GoogleCodeExporter
opened
9 years ago
2
SRS 31 — A command line tool shall be implemented utilising libwarc to check the consistency of WARC-records and their conformance to the WARC ISO standard.
#37
GoogleCodeExporter
closed
9 years ago
2
64-bit compile problem
#36
GoogleCodeExporter
closed
9 years ago
1
SRS 30 — It shall not be possible to use more than one compression schema (including non-compression) within a single WARC file...
#35
GoogleCodeExporter
closed
9 years ago
2
SRS 29 — Libwarc shall support multiple compression schemas, loading a specific compressor at runtime as an external shared library.
#34
GoogleCodeExporter
closed
9 years ago
2
SRS 28 — The default compression format shall be Gzip
#33
GoogleCodeExporter
closed
9 years ago
2
SRS 27 — Libwarc shall support non-compressed WARC-records and compressed WARC-records and files
#32
GoogleCodeExporter
closed
9 years ago
3
SRS 26 — Libwarc shall not use file to memory mapping technology, instead libwarc will explicitly allocate memory as needed.
#31
GoogleCodeExporter
closed
9 years ago
3
SRS 25 — The payload (or the WARC-record document itself) are stored on disk, to avoid using memory heap, even for small objects.
#30
GoogleCodeExporter
closed
9 years ago
2
SRS 24 — Libwarc shall allocate minimum memory heap to store WARC-record metadata.
#29
GoogleCodeExporter
closed
9 years ago
2
SRS 23 — Libwarc shall use dynamic heap memory for its internal usage.
#28
GoogleCodeExporter
closed
9 years ago
2
SRS 22 — Developers using libwarc shall not be required to allocate/release memory directly...
#27
GoogleCodeExporter
closed
9 years ago
2
SRS 21 — Libwarc shall encapsulate and handle all memory management when processing WARC-record...
#26
GoogleCodeExporter
closed
9 years ago
3
SRS 20 — Libwarc’s iterators may be combined into composite iterators to enable the developer to more than one search field
#25
GoogleCodeExporter
closed
9 years ago
2
SRS 19 — Libwarc’s generic iterators may be customised for different purposes via callback handlers (i.e. hooks)
#24
GoogleCodeExporter
closed
9 years ago
2
SRS 18 — Libwarc shall provide a WARC-record-type iterator
#23
GoogleCodeExporter
closed
9 years ago
2
SRS 17 — Libwarc shall provide a WARC-record MIME-type iterator
#22
GoogleCodeExporter
closed
9 years ago
2
SRS 16 — Libwarc shall provide a generic iterator, to enable the developer to iterate over all WARC-records and create an abstract WARC-document as a simple container
#21
GoogleCodeExporter
closed
9 years ago
2
SRS 15 —Libwarc shall include ADT objects to handle read operations on ARC-records.
#20
GoogleCodeExporter
closed
9 years ago
2
SRS 14 — Any operations on WARC-records shall be possible using functions accepting the abstract handle as an argument.
#19
GoogleCodeExporter
closed
9 years ago
3
SRS 13 — It shall be possible to release the WARC-record using a destructor.
#18
GoogleCodeExporter
closed
9 years ago
2
SRS 12 — It shall be possible to create a WARC-record using a constructor, which will returns an abstract handle to data representing the WARC-record.
#17
GoogleCodeExporter
closed
9 years ago
2
SRS 11 — Libwarc shall provide an API describing (1) the set of data, and (2) the set of operations that can be performed on the data...
#16
GoogleCodeExporter
closed
9 years ago
2
SVN includes directory named '\' which breaks checkout under cygwin
#15
GoogleCodeExporter
closed
9 years ago
2
SRS 10 — Each peer class shall expose a set a class functions to read, write, and update attributes for the corresponding WARC-record.
#14
GoogleCodeExporter
closed
9 years ago
2
SRS 9 — The attributes of each WARC-record, as per the ISO standard specification, shall have a corresponding attribute in its peer C class.
#13
GoogleCodeExporter
closed
9 years ago
3
SRS 8 — Each WARC-record shall be accessible via a peer C class of the same name.
#12
GoogleCodeExporter
closed
9 years ago
3
SRS 7 — The universal header "warc.h" shall provide normalised interfaces to enable developers to create valid and compliant WARC-records...
#11
GoogleCodeExporter
closed
9 years ago
3
SRS 6 — The interfaces in libwarc shall ensure that any changes to the library, will not affect any tool or application based on libwarc.
#10
GoogleCodeExporter
closed
9 years ago
2
SRS 5 — The universal header "warc.h" shall ensure that deprecated function calls and changes to the library are notified at compile time.
#9
GoogleCodeExporter
closed
9 years ago
3
Previous
Next