I think Juergen's point is that this is a workaround: you
can cache iAppli, but not pages.
I'd like to know how sizes of cHTML source and resulting
iAppli binaries compare. My understanding (courtesy
of Harry Behrens, and possibly phone-dependent)
is that API calls are "late-bound" - the actual character
string representation of the method call is still in
the downloaded binary. That would seem to bulk
it out a little, to the extent that cHTML content is
tag-text, anyway.
-m
----- Original Message -----
From: "Mika Tuupola" <tuupola@appelsiini.net>
To: <keitai-l@appelsiini.net>
Sent: Thursday, May 17, 2001 9:30 PM
Subject: (keitai-l) Re: Useful inventions...for conserved news?
> On Thu, 17 May 2001, Juergen Specht wrote:
>
> > -- Fujitsu Ltd. and TurboLinux Japan KK said they are releasing
> > the beta version of a jointly developed tool which converts
> > Compact-HTML codes for i-mode into i-mode-based Java source codes.
> >
> > This version focuses a function of converting the user interface.
> > One page of HTML will be converted into a Java program that produces
> > a similar display image on the i-mode screen.
>
> Errr... Now whats the point? I could imagine the the on the fly
> generated javacode is larger in the bytes than what the
> chtml page would be.
>
> If you combine the size of the browser and the chtml page
> the resulting size in bytes is larger though so this would
> make sense only with phones who dont have browser but can
> run Java.
>
> What am I missing in here?
>
>
> --
> Mika Tuupola http://www.appelsiini.net/~tuupola/
>
>
> [ Did you check the archives? http://www.appelsiini.net/keitai-l/ ]
>
>
[ Did you check the archives? http://www.appelsiini.net/keitai-l/ ]
Received on Fri May 18 08:58:54 2001