headers
Rodent of Unusual Size | 7 Aug 2003 05:46

[STATUS] (apr-serf) Wed Aug 6 23:46:47 EDT 2003

APR-SERF STATUS:						-*-text-*-
Last modified at [$Date: 2002/07/01 15:51:57 $]

Release:

RELEASE SHOWSTOPPERS:

	We need code.  This project's goal is to create an http
	client library.

  * web pages (go to apr-site)

  * decide on layout of the repository (e.g. subdirs)
    Greg thinks: prolly the following: /build, /include, /docs, /test, 
		 /core, and some for high-level items (maybe /filters
		 and /utils)
    Justin says: Fine with me except /core can't be used as autoconf
                 trounces this directory via rm -rf - how about /base?

  * set up config/build structure based on apr-util
    (take this opportunity to simplify again; hopefully to fold these
     simplifications back into apr(-util))

  * release scripts (in /build) (and a how-to-release.txt in docs/)

RELEASE NON-SHOWSTOPPERS BUT WOULD BE REAL NICE TO WRAP THESE UP:
Permalink | Reply | 0 comments |
headers
Rodent of Unusual Size | 14 Aug 2003 05:47

[STATUS] (apr-serf) Wed Aug 13 23:47:31 EDT 2003

APR-SERF STATUS:						-*-text-*-
Last modified at [$Date: 2002/07/01 15:51:57 $]

Release:

RELEASE SHOWSTOPPERS:

	We need code.  This project's goal is to create an http
	client library.

  * web pages (go to apr-site)

  * decide on layout of the repository (e.g. subdirs)
    Greg thinks: prolly the following: /build, /include, /docs, /test, 
		 /core, and some for high-level items (maybe /filters
		 and /utils)
    Justin says: Fine with me except /core can't be used as autoconf
                 trounces this directory via rm -rf - how about /base?

  * set up config/build structure based on apr-util
    (take this opportunity to simplify again; hopefully to fold these
     simplifications back into apr(-util))

  * release scripts (in /build) (and a how-to-release.txt in docs/)

RELEASE NON-SHOWSTOPPERS BUT WOULD BE REAL NICE TO WRAP THESE UP:
Permalink | Reply | 0 comments |
headers
mark | 17 Aug 2003 04:00
Picon

snapshot download url


To accomodate a project I am working on, I have put up a auto-syncing
snapshot download. It checks out anoncvs twice a day from:
	:pserver:anoncvs <at> cvs.apache.org:/home/cvspublic
and tars it up as apr-serf_snapshot.tgz
here:

	http://node.to/mirror/src/apr-serf_snapshot.tgz

I've written an apache module that provides a full feature load balancer,
and am finding the apr-serf library very handy in writing a monitoring and
management utility (the module is manageed via http requests to it).

  mark <at> node.to  http://node.to/~mark   7123 3F7B 10EC 7122 2F8B
  http://node.to/keys/mark.asc         B474 B09D 6ED7 3FB0 09E8
Permalink | Reply | 2 comments |
headers
Thom May | 17 Aug 2003 04:09

Re: snapshot download url

* mark (mark <at> node.to) wrote :
> 
> To accomodate a project I am working on, I have put up a auto-syncing
> snapshot download. It checks out anoncvs twice a day from:
> 	:pserver:anoncvs <at> cvs.apache.org:/home/cvspublic
> and tars it up as apr-serf_snapshot.tgz
> here:
> 
> 	http://node.to/mirror/src/apr-serf_snapshot.tgz
> 
I've just added apr-serf to apache's snapshot system; it should appear on
http://cvs.apache.org/snapshots/apr-serf/ in the next couple of days.
Cheers
-Thom
Permalink | Reply | 0 comments |
headers
Cliff Woolley | 17 Aug 2003 07:43
Favicon

Re: snapshot download url

On Sat, 16 Aug 2003, mark wrote:

> snapshot download. It checks out anoncvs twice a day from:

Thanks... though twice a day is maybe a little overkill since apr-serf
hasn't had any commits in many months.  :)

--Cliff
Permalink | Reply | 0 comments |
headers
Rodent of Unusual Size | 21 Aug 2003 05:46

[STATUS] (apr-serf) Wed Aug 20 23:46:39 EDT 2003

APR-SERF STATUS:						-*-text-*-
Last modified at [$Date: 2002/07/01 15:51:57 $]

Release:

RELEASE SHOWSTOPPERS:

	We need code.  This project's goal is to create an http
	client library.

  * web pages (go to apr-site)

  * decide on layout of the repository (e.g. subdirs)
    Greg thinks: prolly the following: /build, /include, /docs, /test, 
		 /core, and some for high-level items (maybe /filters
		 and /utils)
    Justin says: Fine with me except /core can't be used as autoconf
                 trounces this directory via rm -rf - how about /base?

  * set up config/build structure based on apr-util
    (take this opportunity to simplify again; hopefully to fold these
     simplifications back into apr(-util))

  * release scripts (in /build) (and a how-to-release.txt in docs/)

RELEASE NON-SHOWSTOPPERS BUT WOULD BE REAL NICE TO WRAP THESE UP:
Permalink | Reply | 0 comments |
headers
Rodent of Unusual Size | 28 Aug 2003 05:46

[STATUS] (apr-serf) Wed Aug 27 23:46:44 EDT 2003

APR-SERF STATUS:						-*-text-*-
Last modified at [$Date: 2002/07/01 15:51:57 $]

Release:

RELEASE SHOWSTOPPERS:

	We need code.  This project's goal is to create an http
	client library.

  * web pages (go to apr-site)

  * decide on layout of the repository (e.g. subdirs)
    Greg thinks: prolly the following: /build, /include, /docs, /test, 
		 /core, and some for high-level items (maybe /filters
		 and /utils)
    Justin says: Fine with me except /core can't be used as autoconf
                 trounces this directory via rm -rf - how about /base?

  * set up config/build structure based on apr-util
    (take this opportunity to simplify again; hopefully to fold these
     simplifications back into apr(-util))

  * release scripts (in /build) (and a how-to-release.txt in docs/)

RELEASE NON-SHOWSTOPPERS BUT WOULD BE REAL NICE TO WRAP THESE UP:
Permalink | Reply | 0 comments |

Gmane