|
Newsletters
|
|
|
|
|
| Wireless Developer Network Mailing List |
| |
| Mailing List Archives |
| Subject: | Re: MobileLBSList: Article slamming wireless web |
| Date: |
10/30/2000 08:40:04 AM |
| From: |
robert.cayzer@my.arthurandersen.com |
|
Hi Hubert,
My understanding is:
- SOAP is a standard developed (IBM, MS) for wrapper (aka envelope)-based object
messaging and is currently bound the HTTP protocol though it theoretically is
not tied in with any transport. The great thing about it is it's "open"
reference passing model, hence it's reliance on HTTP. But there are allowances
for SOAP on RPC
- C-based RPC in it's raw form does not support reference calls smoothly without
some structure for distributed garbage collection, hence SOAP on RPC doesn't
wash too well. Other RPC hybrids (Jini / HAVI) support it, but their service
discovery is based on their homogenious platform. okok, Java is an open standard
which runs on any os. But as a language it works in homogeneous manner - ie: for
handsets, appliances, devices, terminals java must exist globally & all the time
for Jini to work ubiquitously
- The problem with SOAP on HTTP is HTTP. HTTP is not every efficient as it was
not designed / optimised for high-speed, peer systems with lots of objects
talking to each other in real time. I hope HTTP-NG will fix that.
cheers,
rob.c.
To: Robert Cayzer
cc: mobilelbslist@wirelessdevnet.com
Date: 10/29/2000 11:28 PM
From: hubert@cs.nyu.edu
Subject: Re: MobileLBSList: Article slamming wireless web
What is this RPC-server ( remote process call?)
standard's relevance to the SOAP? Any at all?
On Sat, 28 Oct 2000 robert.cayzer@my.arthurandersen.com wrote:
>
>
> Hi,
>
> RPC-Service discovery is the reason for using HAVI (Philips/Sony), Jini (Sun).
> It is also very likely (imo) to be in WAP-NG. A large element behind this is
not
> just to download apps from central servers, but from a range of trusted
> distributed servers and peers (clients) with needed data and applications -
> especially those within closer proximity. But this goes beyond the assumption
of
> single-hop wireless loops to/from publicly run PLMNs.
>
> Scott: I don't think I've seen the new SIM stuff yet from 3GPP, I think it's
> still in draft mode for v5 right (is it - 22.038?) Do you have a copy/url for
> it?
>
> cheers,
> rob.c.
>
>
> To: Shubhro.Banerjee@techspan.com, bryan@wirelessdevnet.com,
> mobilelbslist@wirelessdevnet.com
> cc: (bcc: Robert Cayzer)
> Date: 10/28/2000 07:35 AM
> From: sguthery@mobile-mind.com
> Subject: Re: MobileLBSList: Article slamming wireless web
>
>
>
>
> Good idea! RPC to the SIM Toolkit API
> is what the new 3GPP SIM Interpreter
> standard is all about.
>
> Cheers, Scott
>
> ----- Original Message -----
> From: <Shubhro.Banerjee@Techspan.com>
> To: <bryan@wirelessdevnet.com>: <mobilelbslist@wirelessdevnet.com>
> Sent: Friday, October 27, 2000 5:45 PM
> Subject: RE: MobileLBSList: Article slamming wireless web
>
>
> The fundamental issue of the wireless web : low real estate, even lower
> bandwidth and a legacy behavioral pattern from using a computing device to
> access and POST pages and forms are the quintessential problems with
> wireless. Once the embedding of even limited simple instruction sets on the
> device (and the phone)that are etched to a particular API becomes pervasive
> the "irritation" with wireless web will be over.
>
> Could we do RPC's over the phone/ PDA that tunnel thru existing enterprise
> firewalls and kickoff remote services by some kind of dynamic
> discovery...could be the panacea for wireless baiters..
>
> Thanks
>
> -----Original Message-----
> From: Bryan Morgan [mailto:bryan@wirelessdevnet.com\
> Sent: Thursday, October 26, 2000 10:58 PM
> To: mobilelbslist@wirelessdevnet.com
> Subject: MobileLBSList: Article slamming wireless web
>
>
> Interesting article at WebReview.com:
> http://webreview.com/pub/2000/10/27/feature/index03.html
>
> Despite protestations from the wireless crowd, what matters at the end of
> the day is the perception of the general public. It's clear that many
> carriers (and software companies) are going back to the drawing board to
> rethink their marketing and product strategies. Any thoughts on what's
> needed to help the usability of the wireless web? I've got my own opinions
> but I already have a platform to voice those on :-)
>
> Bryan
>
> ====================================
> Bryan Morgan
> Managing Editor, Wireless Developer Network
> http://www.wirelessdevnet.com
> bryan@wirelessdevnet.com
> Phone: (850) 232-3439
> Fax: (850) 897-1001
> EMail Page: 8502323439@page.nextel.com
> ====================================
>
>
>
> To unsubscribe, write to mobilelbslist-unsubscribe@geocomm.com
> ________________ |
|
|
