> > >> MvB> Cramming a HTML-parser into 64K is quite a job. Adding a full > > >> MvB> TCP/IP stack won't fit. > > IMHO a BASIC interpreter is more difficult and needs more intelligence > (syntax checking !!!) then a parser which reads lines and acts according the > tags. The Basic V2 interpreter takes about 9-10 KB of strict machine-language ROM code. And HTML is growing more and mode complex... > > MRDOM> WOP! The pages! Especially today, some pages can take 100+ KB! > > > Everything going to have big (and fast enough) storage (like RAMDisk or > HDD) > > and stock C64/C128 can do small web browser things (I mean much better > > possibilities than WAP browsers :-). > > This is where Frank is absolutely right: store the incoming stuff on a, > preferable fast, medium. The only problem I forsee is the "fast". A standard > 1541 stores about 400 Bytes/second. A 9600 BAUD means plm. 900 Bytes/second; > we have a traffic jam. (I forget the possibility of storing it in native RAM > for the moment) Maybe a C/128 with a 1571 can take that data load. Anyway, just for fun, I remember about someone setting up a WAP browser on a VIC-20... will take out the exact URL if someone needs it! > > About images. C64/C128 in graphic mode can display 16 different colors > > (without tricks). Thus no need to cache or store 256 or more color images > > and reload/resample every time. Just store in resized downsampled 16 > > colors and voila. 320x200 image takes 8K of RAM. RAM disk or 1541 > > disk can fit 21 of such file (without of any compression algorithm). This > > means 21 screens of graphics. > > Also correct. But an initial load is needed and nowadays files ain't small. > Not having a REU or equivalent could get you in trouble. More: during the test of a PC browser for Dos called Webspyder on a 486, I found myself in the strange condition of not being able to use a standard VGA (640x480) mode because the video board wasn't recognized as a SVGA and the browser needed 256 colors. I found myself into a X-mode very similar to the C/64 resolution, and that was an experience I would never recommend to anyone. If you're skeptical about my impressions, I strongly suggest to find out a Macintosh Classic or Classic II (512x342 screen) and try out a WWW browser upon there... :-( Anyway, hearing about a stock C64 as a Web browser, I immediately thought that was feasible for textmode only. > > Lynx is placed under GNU GPL, so the sources are available almost > > everywhere. Stripping away some (many) features, maybe... > > This is a PC-browser, isn't it? It is a browser for textmode, available as open source. As far as I know, it was ported on multiple systems, so it's not just PC-related. I'm not sure whether it's in the NetBSD for Amiga standard distribution or not. :-) Obviosuly, versions for DOS (and probably Win32) exist, too. My initial idea was that Lynx, and only Lynx, is good to surf the Net with a C/64. The only choice would be where to run it: on a C= 64/128 or on a Unix host the C= is connected to? > What is "CGI" and "ISP"? CGI is "Common Gateway Interface": the standard methods to pass parameters to a page (GET and POST), i.e. to a program that will show you a page resulting from those data. Often, is called a CGI a program that materially performs the action of taking those data and do something related to them, giving back the results page. Historically, most CGI are Unix scripts (Dos users would say "batch files") written in Perl; but this strictly depends on the server. Windows NT can, more likely, use ad-hoc written EXE programs. ISP means, more simply, Internet Service Provider: the company you place your call to when you are dialing the Internet. yo, RDO - This message was sent through the cbm-hackers mailing list. To unsubscribe: echo unsubscribe | mail firstname.lastname@example.org.
Archive generated by hypermail 2.1.1.