On Sun, 2001-11-25 at 14:34, Jason Rennie wrote: > Where your problem might be is with network and host byte order ?
Doesn't apply in this case - I think JPEG internally distinguishes between BE and LE formats, but it may be fixed to one of them - at any rate, mucking with the structure of a valid JPEG isn't likely to help. As an example from mikolaj.tv's webcams: %eris[2]~> telnet eris 39193 13:40 Trying 203.10.70.2... Connected to eris.rcpt.to. Escape character is '^]'. GET /singleframe/ HTTP/1.0 HTTP/1.0 200 OK Content-type: image/jpeg JFIFC .... where JFIFC are the first 5 bytes of the JPEG. Most important thing to check is that you're sending \r\n as line endings, not just \n - and obviously making sure that it's a valid JPEG. m. -- SLUG - Sydney Linux User Group Mailing List - http://slug.org.au/ More Info: http://lists.slug.org.au/listinfo/slug
