[STATUS] (apr-serf) Wed Sep 10 23:47:42 EDT 2003

[Rodent of Unusual Size <Ke...@Golux.Com>]

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:

ssl bucket handling question

[mark <ma...@node.to>]

Why does

serf_bucket_ssl.c:96:        ssl_read_socket(context, buf, buflen);

call ssl_read_socket (which is not in openssl has far as I can see)
instead of SSL_read?

Anyone know?
I'm assuming they are congruent, and I just defined:
#define ssl_read_socket(ctx, buf, len)   SSL_read(ctx, buf, len)

in serf_config.h


--mark



  mark@node.to  http://node.to/~mark   7123 3F7B 10EC 7122 2F8B
  http://node.to/keys/mark.asc         B474 B09D 6ED7 3FB0 09E8