From: Fredrik U. <ul...@gm...> - 2009-08-01 19:14:29
|
> > as for the use case, i have a bot that logs messages for me when i am not > online, and when that bot forwards messages it has been logging back to me, > i receive all messages as though they just got written, although some might > be dating from a week ago. therefore, i want my bot to add a TS field to > each message specifying when it was sent, so that when DC++ receives it, it > displays it with its original timestamp. > Could you not modify your bot to actually store the time, too? So it'd report the time it got the message... (Time would probably enlarge the entirety of messages compared to the TS param, but still.) > another similar example would be a hub that offers an "offline PM" > functionality: send a message to a regged user, and if that user is not > online, the hub logs it and wait for that user to come back to send her your > message. in this case too, the lag is not negligible anymore and there needs > to be a way for the sender of the logged message (be it a hub or a bot) to > tell when the message was originally sent. Actually, I've been using a hub that have that exact functionality. "You have the following messages: 1) PM from <nick>: <msg>, <date/time of message>" -- i.e., it displays the date/time the message was sent (well, obviously received by the hub). Granted, having *exact* time in terms of message sent by client might be useful, but I think the (potential) lag is negligible. (Indeed, the hub is NMDC even...) -- Fredrik Ullner |