| WAP PUSH SI TEST |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through April 08, 2009 ⬆ |
◄ ► |
| Author | Message | |||
| yzhou New member Username: Zy_sakura Post Number: 1 Registered: 02-2009 |
During my test of WAP PUSH SI with NOWSMS,I meet some problems.I would like to ask, Case 1: Send a WAP Push SI with the action: signal-medium, both "SI-ID" and "Created" field set.And then send anther WAP Push SI with the same URL and the same "SI-ID", and "Created" set to a date equal to the one before. Case 2: The same as 1,except that there's no SI-ID preset. Case 3: Send 2 WAP Push SI (one by one) with the action: signal-medium, the same "SI-ID" and the same "URL" fields set but no "Created" information. in these 3 cases above,will the replacement happen or not? And there's another problem with the SI-expires, Case 4: Send a WAP Push SI with the action: signal-medium, and SI-expires set to a date earlier than the MS current date; Then Send another WAP Push SI with the action: signal-medium, and SI-expires set to a date later than the MS current date. We expect that the first message will be deleted automatically,and till the expiration date of the 2nd one, it will also do the same. But in our result,the first one isn't delected, but replaced by the 2nd one. Is it possible or where might be the problem come from? Thank you so much! | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 7749 Registered: 10-2002 |
It really depends mostly on the handset. NowSMS just sets the parameters in the push message, and it is up to the handset to interpret them. (And some of it may depend on the order in which the handset receives the messages.) Case 1: By specification, the second push should replace the first. However, I would suggest that the "created" field in the second push SHOULD be later than the "created" field in the first push in order to avoid ambiguity. If the push client receives a push with the same "SI-ID" as an existing push, but a later "created" time, then the later "created" push should replace the earlier push. Case 2: Without "si-id", the "href" value should be used as an implied "href", and, according to the specification, behaviour should be identical to case 1. Case 3: Based upon my reading of the specification, this does not meet the requirement for "replacement". Some handsets may choose to replace the first push with the second, or to silently discard the second. By a strict reading of the specification, I think both pushes should appear in the inbox without replacement, as the replacement criteria in the specification requires an explicitly set value for "created" in order to qualify for replacement. Case 4: According to the specification, the first message should be silently deleted (not displayed by the mobile), and only the second one should be displayed. If this is not the behaviour that you are seeing ... all I can suggest is experimenting with different phones. Unfortunately, NowSMS only encodes these fields in the push message for the mobile station to interpret them. It would not surprise me to find phones that had bugs in how these actions are interpreted due to sloppy or incomplete client software testing procedures. -bn | |||
