Globally Unique Message Ids | Search |
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ Archive through November 04, 2008 ⬆ |
◄ ► |
Author | Message | |||
RMD New member Username: Thinkfr33ly Post Number: 4 Registered: 02-2007 |
This is more of a feature request than a support question. The message ids returned by NowSMS are essentially integers that are HEX encoded. These obviously are simply incremented as messages go in and out of the system. This presents a major issue when you've setup a failover server in the event that the server that NowSMS runs on dies for some reason. You've got a strong possibility that you'll encounter message ids that have already been used in the past. In a system where message ids are used for things like billing receipt tracking, this is very bad. I'd like to request that NowSMS implement a globally unique identifier system of message ids instead of simple integers. | |||
Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 7110 Registered: 10-2002 |
Hi RMD, I wouldn't see a problem with having an option to add a host name (or other identifier) to the end of the message id. Would that address your need? -bn | |||
RMD New member Username: Thinkfr33ly Post Number: 5 Registered: 02-2007 |
Bryce, Adding a hostname would kinda work. But I think a more complete and robust solution would be to simply generate a globally unique identifier that would never be repeated. This would have many benefits and would allow your customers to develop solutions that would never need to worry about duplicate message ids. There are several Windows APIs that can return GUIDs to you, so adding this would be fairly easy I think. See: http://en.wikipedia.org/wiki/Globally_Unique_Identifier | |||
Nikhil Talwar New member Username: Nik Post Number: 1 Registered: 01-2008 |
Bryce, Have you worked around on this issue of assigning a unique global message ID? We have also been facing issues in handling of duplicate message ids for delivery report tracking. Nikhil |