I suggest that only changes cross the wire and otherwise all read operations
should be performed on a local replicated database.
So, you setup the tunnel for the replicator to operate through and then let
the rest of it be handled as a normal application with a "relatively" local
database.

Jason Wharton
CPS - Mesa AZ
http://www.ibobjects.com

----- Original Message -----
From: "Paul Schmidt" <paul@...>
To: <ib-support@yahoogroups.com>
Sent: Friday, July 13, 2001 11:39 AM
Subject: [ib-support] Hypothetical Situation


> Dear list,
> hypothetical situation, trying to figure which direction to recommend
> on a project.
>
> I have a client with two offices Toronto and Vancouver, and we are
> trying to figure the best game plan.
>
> What do you think of this idea?
>
> Put a big server into the Toronto office, put a fraction of a T1 from
> each office, to the Internet Backbone. Then use a VPN tunnel to
> connect Vancouver to the server in Toronto.
>
> Okay, the $50,000 question, will forcing a transaction through the
> tunnel (roughly a 3000 mile trip, one way) have any ill effects, will
> the tunnel affect the performance of the transaction? Roughly 40% of
> the transactions come from Vancouver, would that be too much tunnel
> traffic? What about adding additional offices, say Montreal, Halifax
> and New York City?
>
> Thanks,
>
> Paul
>
>
>
>
>
>
>
>
>
>
>
> Paul Schmidt,
> Tricat Technologies
> Email: paul@...
> Website: www.tricattechnologies.com
>
> To unsubscribe from this group, send an email to:
> ib-support-unsubscribe@egroups.com
>
>
>
> Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
>
>