Reservation Friend Setup - Operation
|
Top |
· | Skip all site locks & synchronization -- This of course defeats the purpose of real-time 2-way integration, and should only be used for testing or other extreme conditions.
|
· | Initiate locks & synchronization, but don't wait -- This tells Friend what's going on, but ignores any response that might suggest a conflict. Basically this gives Friend a chance to lock out sites you're working on locally, but there is still a chance that an online reservation creates a conflict (e.g. if it's started online but not completed & downloaded before you use the site locally). This should only be used if you're having connection problems that are causing severe delays in responses.
|
· | Do locks & synchronization, and wait/warn if issues before starting the operation -- This could be used if you don't mind waiting for a response before continuing a reservation, for instance. Naturally this should only be used if the response time is fast enough for your comfort. The advantage is that you avoid the possible annoyance of finding out only at the end of making a reservation that the site isn't available online. This is also a viable option if the majority of your reservations are made online at a rapid pace, such that a local reservation is frequently denied due to an online site lock.
|