 |
 |
 |
 |
|
 |
 |
Gravitybox Schedule.NET User’s Guide
Page 19
1998-2004 Gravitybox Software LLC
this.Text = "Gravitybox Schedule.NET Enterprise Test";
}
Each time the schedule is changed, i.e. an appointment is modified, moved, removed,
etc., the schedule event DataSourceUpdated is raised. This informs the container that
the schedule was modified in some way. In the code snippet below we modify the form’s
caption to reflect this state change and notify the user that the schedule has not been
saved to the database. You might also wish to set a variable to be used later to
determine whether schedule needed to be saved.
private void schedule1_DataSourceUpdated(object sender, System.EventArgs e)
{
this.Text = "Gravitybox Schedule.NET Enterprise Test (modified)";
}
Time Zones
One of most useful pieces of functionality available with the Enterprise Server is it ability
to keep track of time zone information. Appointments are displayed based on the time
zone in which they were created. For example if you create an appointment at 11:00AM
in EST and then viewed it on a schedule in the PST, you would see that it is displayed
at 8:00AM. This is the real time of the appointment because 8:00AM PST occurs at the
same time as 11:00 EST. These are all local times. The time is stored in the database in
GMT. This ensures that if you ever move the server to another time zone, your
appointments will still be in tact.
This can cause some confusion if it is not fully understood. Suppose the machine with
the Enterprise Server software exists in PST (GMT-8). Now a client in EST (GMT-5)
creates an appointment at 11:00AM. When you look at the Appointment table in your
database you see that the appointment is scheduled for 3:00PM (15:00). The server sits
in PST so you might expect it to have 8:00AM but it does not. The time is stored in the
database in GMT. When you load appointments from the Enterprise Server it converts
the time to the local time of the client. If you look at the underlying dataset before you
bind it to the client, you will notice that the times are all local to the client. They are not
GMT. If another client in PST opens the schedule, he will see the appointment
scheduled for 8:00AM.
Please note that there is one caveat. The database must be in the same time zone as
the Enterprise Server. If your database server is your web server there is no problem.
However if you have separate web and database server, they must be set to the same
time zone for the times to coordinate correctly. This should not be an issue since the
web server needs a direct connection to the database in any case, so they will most
likely be at the same location.
Security
The data that is passed back-and-forth can be secured. The controller property
“WebServiceURL” can be prepended with “https” instead of “http” for secure
transmission. This ensures that all data is sent to the server via the HTTPS protocol.
 |