WAP Push

WAP Push SearchSearch
Author Message
Damian Glover
Posted on Wednesday, November 20, 2002 - 03:08 pm:   

If I send a WAP Push message to a user (NB I dont mean an MMS notification, but a simple WAP Push message) and the user's handset does not support WAP Push, what happens?
Is the SMS delivered to the phone in any case, but the "click to connect to url" option does not work?
Is it possible to display an alternative message if the phone does not support WAP Push, eg "go to this url on the internet to view the page"?
Bryce Norwood - NowSMS Support (Bryce)
Posted on Wednesday, November 20, 2002 - 03:24 pm:   

Hi,

If the phone doesn't support WAP push, what happens tends to depend on the phone. Usually what happens is that the phone indicates that it received an unknown binary message ... and most of the phones that I have seen still allow you to open the message. You'll see some junk characters, along with the text of the alert and the URL.

One word of advice if you're thinking that you might end up sending some WAP push messages to phones that don't support it ... keep the text and the URL short. If the text + the URL + the WAP push overhead (which is maybe 20 to 30 characters) exceeds 140 characters, then it has to be sent out as a concatenated SMS message which means an older phone would see it as multiple messages.

-bn
damian glover
Posted on Wednesday, November 20, 2002 - 05:54 pm:   

thanks - so the message text would be something along the lines of "click here to view content or visit www.blahblah.com/etcetc/picture.gif"?
damian glover
Posted on Wednesday, November 20, 2002 - 06:01 pm:   

one more question Bryce - if the wap page linked to by the WAP push message contains content not supported by WML, such as a gif image, then I understand that what happens next (assuming the users phone supports WAP Push) depends on the wap gateway. My understanding is that only WAP gateways that support Accept Headers will deliver the WAP page in this instance - is that right, and do you have any more info on how this works?
cheers,
damian
Bryce Norwood - NowSMS Support (Bryce)
Posted on Thursday, November 21, 2002 - 02:35 pm:   

Right. You supply message text and a URL, just keep them relatively short to fit into a single message.

Typically in a push, you're going to push a link to a WML page, and that WML page would include an img reference to an image. (If your push link was directly to an image, it may or may not work. It may work just fine, but with the variety of browsers out there, I'd put a WML wrapper around it to be safe.)

Regarding "accept" headers ... what happens is that the WAP browser in the phone specifies what content types it will accept when it makes the request. The WAP gateway passes those headers along to the content server (beware, I've seen WAP gateways do this in two different ways ... most pass a single Accept: header with a comma delimited list of content types, but I've also seen some pass multiple Accept: headers with one content type per header).

The content server is the one that decides what to do. If the content being requested is not of an accepted MIME type, the web server usually returns error 406. In some cases, if the content server returns some content of an unsupported type, the WAP gateway will be the one that rejects it ... but usually it is the web server.

I'm not an expert with ASP, but you could probably have the IMG reference an ASP link ... have the ASP look at the Accept: header ... if GIF is supported, send "image/gif" content, and if not, send "image/vnd.wap.wbmp" (legacy WAP monochrome bitmap) content.

-bn
deepak
Posted on Thursday, November 28, 2002 - 10:19 am:   

what exactly is a legacy user . i am a mms user when will i be a legacy sms user
Bryce Norwood - NowSMS Support (Bryce)
Posted on Thursday, November 28, 2002 - 03:03 pm:   

Well, in this case, what I mean is that "image/vnd.wap.wbmp" is a legacy format for graphics on older WAP browsers, while newer browsers are supporting GIF and JPG.

The definition for legacy is "something handed down from an ancestor or a predecessor or from the past".

However, in the mobile phone world, this term is used a lot to refer to older technologies.

I don't think SMS is going anywhere, it's still the best way to send a quick text message to another mobile phone. But as MMS becomes a standard feature on all mobile phones, the day will come that SMS-only phones would be referred to as "legacy handsets".

Not sure if that helps explain anything or not ...