I just thought I should repsond to all those who gave me idea, code, resources to help with the 28.8k modem friendly API..
 
So: Thank you all.
 
While I have not defined an absolute solution I do believe that the solution lies in making a "modem" version of the api.
This will entail splitting the files further to isolate only that functionality needed, even removing prototypes for functions that are not needed
in a particular apllication. As well as splitting them by Browser.
 
While I agree that splitting the api by browser would result in redundant source code, it would still result in a smaller download on a pre user basis.
 
Keep in mind that each page of the site can not exceed 32k in size, including graphics (tho not many graphics to be sure).
 
The final solution will most likely invlove intergrating Gzip-on-the-fly functionality as well.
 
Again, thank you everyone.
 
 
 
 
Doug Melvin
Programmer/Analyst
Creative-Workshop.com
(613) 236-5556

Reply via email to