RE: [PHP-DEV] RE: [PHP4BETA] Small footprint PHP
| From: | Samuel Liddicott | Date: | Mon, 20 Dec 1999 14:36:39 +0000 |
| Subject: | RE: [PHP-DEV] RE: [PHP4BETA] Small footprint PHP | ||
| References: | 1 | Groups: | php.version4 |
| Request: | Send a blank email to php-version4+get-8222@lists.php.net to get a copy of this message | ||
> -----Original Message-----
> From: Manuel Lemos [mailto:mlemos@acm.org]
> Sent: Saturday, December 18, 1999 04:46 PM
> To: Samuel Liddicott
> Cc: php3@lists.php.net; php4beta@lists.php.net
> Subject: Re: [PHP-DEV] RE: [PHP4BETA] Small footprint PHP
>
>
> Hello Samuel,
>
> On 14-Dec-99 11:38:08, you wrote:
>
> >> A WAP/WML based interface would be ideal because that is the current
> >> standard that is solidifying for handheld based applications. To
> >> make that
> >> work offline there must be a Web like server that may run in
> the handheld
> >> so that using a WAP browser the user may interface with the necessary
> >> applications regardless of the type of handheld device.
>
> >I don't think there is ANY chance of a WAP server in many handhelds. The
>
> Forget all hand-helds. Think just of Palm Pilots which are
> already comming
> with 4MB of RAM and you can already seen a significant market.
>
> Anyway, if is there already lite versions of IBM DB2 and Oracle 8, why not
> a Web server too which can be is much simpler?
>
>
> >best I think we can hope for is some local persistant storage
> and then make
> >use of the cut-down JavaScript that WAP provides to queue up requests to
> >send later.
>
> I can't see where you may queue requests with Javascript. Only the
> upcomming version of WAP spec will support cookies.
Thats why I said "some local persistant storage"
> >Otherwise, work live.
>
> That's what we do today but that costs money to be online and sometimes it
> is not possible at all.
But with WAP? Hmm, maybe - I was thinking of WAP in the Nokia 7110 which
supports sort of "extra" layer of comms for the WAP.
> >I see PHP being used more, but still at server end. Getting
> into different
> >PHP versions accross some non-upgradable handhelds will be a
> nightmare for
> >developers, and make it hard to use.
>
> I don't see why not. PHP is purely C code. It could well be
> built for the
> Palm Pilot as long as some POSIX calls are replaced by something more
> portable.
Palm pilot maybe, but I'm saying in non-(or hard to) upgradable handhelds
will results in a wide range of php versions. For server side code, the
administrator can update php when requried. I think this will not happen so
often in the consumer market.
Sam