Re: [evolution-patches] Patch for Evolution GW backend - minor fixes in the code

[Rodrigo Moya <rodrigo ximian com>]

On Tue, 2004-01-27 at 09:14 -0500, JP Rosevear wrote:
> On Tue, 2004-01-27 at 05:30, Rodrigo Moya wrote:
> > On Mon, 2004-01-26 at 16:42 -0500, JP Rosevear wrote:
> > > On Mon, 2004-01-26 at 02:45, Harish Krishnaswamy wrote:
> > > > hi,
> > > > 
> > > > The following patch contains code added to return UTC as the default
> > > > internal time_zone for GW calendars, changes in the parsing of the
> > > > response elements aligned to changes in the server implementation
> > > > and fixes for compiler warnings.
> > > 
> > > The default time zone is settable by the client, its not meant to be the
> > > default of the server.
> > > 
> > > However, now that i think about it though, since all ecal's share the
> > > same backend instance, this is quite evil, since the ecal's could be
> > > clobbering each others default timezone.  Perhaps the default timezone
> > > should be kept client side and passed into calls where appropriate.
> > > 
> > well, since the clients will always call set_default_timezone on the
> > backend to set the timezone to the one stored in the configuration, I
> > can't see why this would be a problem. I mean, all backends for a given
> > user will all have the same timezone, if the calendars were loaded from
> > the GUI.
> 
> This is why we haven't run into this before, Evolution has been the only
> client, although you might be right that everyone will want the user set
> timezone anyhow.
> 
right, I think what we need is an API to get that setting as well as any
other interesting config setting other clients might need. Thus, we
could assume all e-d-s clients will be using the same settings, and
thus, the same timezone.

cheers