Re: [gopher] gopher++ (gopher1) protocol
On Sun, Jan 10, 2010 at 11:46 PM, Kim Holviala <kim@holviala.com> wrote:
>
> The server MUST be able to convert all image resources to GIF, PNG and JPEG
> formats. A client SHOULD not request for any other format than those three.
>
What's with the vector hate?
> The server SHOULD be able to convert PDF and PostScript resources to the any
> of the above three image formats and to plain text. A client SHOULD not ask
> for anything else.
>
What about rtf, doc and docx?
> The server SHOULD be able to convert all audio resources to either WAV, MP3
> or OGG Vorbis. A client SHOULD not ask for any other format.
>
What about us who have to have our audio in a lossless format?
> The server SHOULD be able to convert all video resources to either MPEG or
> OGG Theora. As video transcoding is CPU-intensive and video formats are a
> moving target, the server is not obligated to obey client requests for video
> formats. A client SHOULD not ask for anything else than MPEG or OGG Theora,
> or "application/octet-stream" if it wants the original video stream.
>
Why not h.264?
You can make it quite small and still retain awesome amounts of quality.
On Mon, Jan 11, 2010 at 6:35 PM, Cameron Kaiser <spectre@floodgap.com> wrote:
> I support putting much of the work on the server, because I think Gopher's
> biggest benefit is a VIC-20 could be made to be a gopher client.
Let's not forget that the same machine can be a gopher server!
_______________________________________________
Gopher-Project mailing list
Gopher-Project@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/gopher-project
Reply to: