| Pushing a .gif file to a wap phone... |  Search
|
|
NowSMS Support Forums ⬆ WAP Technical Discussions (unsupported) ⬆ Archive through December 08, 2004 ⬆ |
◄ ► |
 Closed: New threads not accepted on this page |
|||
| Topic | Posts | Last Post | |
| Closed: New threads not accepted on this page |
| Author | Message | |||
| Anonymous |
I have a quick overview of wap push and get a problem. Is it possible to send a push to bearer a .gif color image? (just like sending a nokia picture message) I hope the solution is not a SI/SL push, because not all of the receivers subscribes the GPRS service. | |||
| Bryce Norwood - NowSMS Support |
I assume that you are referring to a WAP push message where you would actually include the "image/gif" content in the push itself? This, of course, is in contrast to an SI, SL or MMS notification push, all of which reference an external URL. It has been a couple of months since I tried doing this, but I didn't have any luck. I tried a few phones that I had access to, and they all ignored the message completely. I've also tried sending push messages with compiled WML content, but haven't gotten very far with that either. -bn | |||
| Comete |
Hi .. as my understand, this custom push message should take the HTTP or WSP to do it, such as HTTP POST. so, the PPG and Terminal should support the SIR, SIA,TO-TCP and PO-TCP. The kep point is the SIR/SIA format, especially the Format and structrue of SIR. After the IP/TCP connection is Up between the Terminal and PPG, you can push any MIME type content to terminal. BR/Comete | |||
| Kent Williams |
Comete, You are correct. It is just very limited in current device implementations in the world of WSP push. Our experience has been that although the specifications give examples of push with different MIME types, most phones only support push of SI or SL (application/vnd.wap.sic or application/vnd.wap.slc) content. MMS compatible terminals also support application/vnd.wap.mms-message, and then there are some supporting OMA provisioning content, DRM, etc. Basically, the terminals only seem to be supporting the content types that have been designed especially for push. Send an "image/gif" or a WML page, and the message is ignored because the push client does not understand that content type in a push context. I agree that based upon the specifications, it should be like you describe ... the unfortunate reality is that the real world implementations have not been as flexible as the specifications. Cheers! - Kent Williams Now Wireless Support | |||
