Results 1 to 4 of 4
  1.    #1  
    Do you guys run in high-bit or 256 color mode? Have you noticed a difference? The source image has to be the same so I can't imagine it'll save any download time, but it might be a bit easier on the hardware, but I can't imagine the difference between displaying 256 vs 16 bit would be all that much, even for a 33Mhz.

    The setting says "16-bit - Slowest" "256 Color - Slower", making one think 16 bit is slower.

    What do you guys think about this?
  2. #2  
    Saves time & cache. It all goes through the Handspring proxy. I use hicolor, the quality of 256 is too poor. I wish they had an option like Xiino where you could pick no-images, but had a menu shortcut to load images if you decide you wanted them on a particular page.
  3.    #3  
    So you think that setting controls how the proxy compresses the picture?
  4. #4  
    Originally posted by BrianV
    So you think that setting controls how the proxy compresses the picture?
    Yes, it controls a parameter which is sent to the proxy when Blazer requests an image. Here is a portion of a request to microsoft.com.

    An 8-bit (256 color) Blazer request:

    GET /a=iVa0KPTA&c=29BA47970C38DCD0F05F1FEE12529534/http/80/microsoft.com/homepage/gif/bnr-microsoft.gif HTTP/1.1
    user-agent: Blazer/2.1.4 (Color; 8-bit)
    Accept-Language: en
    Host: 64.75.2.12
    Connection: Keep-Alive
    x-wap-profile: http://device.sprintpcs.com/handspri.../Blazer211.rdf

    That is just one request of many in the WAP stream. Total received size was 25,310 bytes.

    A 12-bit (so called hicolor) Blazer request:

    GET /a=iVa0KPTA&c=29BA47970C38DCD0F05F1FEE12529534/http/80/microsoft.com/homepage/gif/bnr-microsoft.gif HTTP/1.1
    user-agent: Blazer/2.1.4 (Color; 12-bit)
    Accept-Language: en
    Host: 64.75.2.12
    Connection: Keep-Alive
    x-wap-profile: http://device.sprintpcs.com/handspri.../Blazer211.rdf

    Total stream size 31,013 bytes.

Posting Permissions