From: Michael Sweet <mike@easysw.com>
To: Discussion for Spool/Job/Queue API subgroup
<printing-spool@freestandards.org>
Cc: printing-announce@freestandards.org,
printing-architecture@freestandards.org
Subject: [Printing-architecture] Re: [printing-spool] PAPI Source code on SourceForge
Date: Fri, 06 Feb 2004 17:17:06 -0500 [thread overview]
Message-ID: <40241262.20401@easysw.com> (raw)
In-Reply-To: <40240483.B2A8686@Sun.COM>
Norm Jacobs wrote:
> ...
> Since Shawn Pratt is the only listed project administrator for the
> openprinting project on SourceForge and his email bounced, I have
> initiated a "takeover" request for the project so that I can
> administrate it (add administrators/developers/content/...). In the
> meantime, here are some specifics about what I have delivered.
Great, I've sent several requests to Shawn to be added to the
project with no response; it will be nice to actually start
developing the code again...
> ...
> port). PAPI over IPP is in the plan and will likely use the IPP support
> from the Apache IPP listener module, but we need to find an http library
> to use first.
I'd like to (again) volunteer the CUPS HTTP and IPP code; it is
fast, stable, supports TLS and SSL, and it substantially smaller
than any other code I've seen.
--
______________________________________________________________________
Michael Sweet, Easy Software Products mike at easysw dot com
Printing Software for UNIX http://www.easysw.com
prev parent reply other threads:[~2004-02-06 22:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-06 21:17 [Printing-architecture] PAPI Source code on SourceForge Norm Jacobs
2004-02-06 22:17 ` Michael Sweet [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=40241262.20401@easysw.com \
--to=mike@easysw.com \
--cc=printing-announce@freestandards.org \
--cc=printing-architecture@freestandards.org \
--cc=printing-spool@freestandards.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.