Package maintainers and Hackage trustees are allowed to edit certain bits
of package metadata after a release, without uploading a new tarball.
Note that the tarball itself is never changed, just the metadata that is
stored separately. For more information about metadata revisions, please
refer to the
Hackage Metadata Revisions FAQ.
| No. |
Time |
User |
SHA256 |
| -r2 (http-listen-0.1.0.0-r2) |
2015-10-05T13:55:40Z |
akrasner |
968de91e5c6c468a62f8f5bff6b465dea5fcd0d33b024dc81df1a9cea9beb2ef
|
|
Changed source-repository
from source-repository head
type: darcs
location: http://dev.rel4tion.org/fr33domlover/http-listen
to source-repository head
type: darcs
location: http://hub.darcs.net/fr33domlover/http-listen
|
| -r1 (http-listen-0.1.0.0-r1) |
2015-08-05T23:35:25Z |
akrasner |
3fcb0a5c155c41513cf81c4cd5058be331d56aed083a3f42892feef452a0cd8b
|
|
Changed description
from In HTTP connections, there is a client side which sends requests (such as GET
and POST), and a server side which receives and parses them. Often, the
server side is a web server which responds to requests by sending some HTML
pages back. But sometimes it's just a listener.
For example, a Git server may offer web hooks. It could send a POST request
whenever a commit is made, or a new repository is created. You then set up a
program that listens to these POSTs and reacts by reporting them to the
project's IRC channel or a mailing list.
Most HTTP packages assume a typical web server which handles requests by
returning HTTP responses. This package tries to fill a gap by providing an
API for simple listeners which don't necessarily serve web pages, and can do
things like reporting to IRC.
Some features are missing and will be added soon:
* Connection timeouts
* Logging (currently errors are written to stdout, no other logging done)
to In HTTP connections, there is a client side which sends requests (such as GET
and POST), and a server side which receives and parses them. Often, the
server side is a web server which responds to requests by sending some HTML
pages back. But sometimes it's just a listener.
For example, a Git server may offer web hooks. It could send a POST request
whenever a commit is made, or a new repository is created. You then set up a
program that listens to these POSTs and reacts by reporting them to the
project's IRC channel or a mailing list.
Most HTTP packages assume a typical web server which handles requests by
returning HTTP responses. This package tries to fill a gap by providing an
API for simple listeners which don't necessarily serve web pages, and can do
things like reporting to IRC.
Some features are missing and will be added soon:
* Connection timeouts
* Logging (currently errors are written to stdout, no other logging done)
|
| -r0 (http-listen-0.1.0.0-r0) |
2015-08-05T23:32:29Z |
akrasner |
b38390559644219f9ccd6a8fc9b55f4788e9356876ad5281f0cc27ee4fe9f77a
|
|
|