[JDEV] Routes, etc..

[Colin Davis]

Thomas Charron wrote:
> 
>   There is one more thing that we need to add here.  In order to get the client
> data of when the 'client' applicaiton sent, we'll need one of two things:
> 
>   The only way to get the CLIENTS timezone, and not that of the 'upstream
> transport' will be if the client adds a node entry to the route tag.
> 
>   Either that, or the first transport to recieve the message fills in the
> timezone for the client from preferences, and that can be used to get it.

Agreed. Either way is acceptable, but I favor the first, for the reason
stated below.

> 
>   Actually, thinking about it, the routing is one thing, but getting the end
> users timezone would almost turn into an Info/Query solution, where the end
> client would request the timezone data.

Some people did not like this, as timezone may change between
messages,and the recieving client would hae no way of knowing when to
update. 
That is why I am in favor what I previously wrote, where the sending
client would modify it's timestamp tag (or whatever) including it's
timezone _when it had changed_
This would be placed on only the first timestamp, which would be sent by
the client.

> 
>   I think people are confusing several things here.  routing is only to
> timestamp messages as they go thru the system, not to resolve the timezone of
> the client..  We can tag it at the start, but the only reliable way would be to
> have it in one of the I/Q tables..
> 

These are different, but similiar. The timestamp could be modified by
the client, as I had said, to includ the timezone. This might be more
appropiate somewhere else, however.