Subject | RE: [firebird-support] Re: Very slow connection over the Internet |
---|---|
Author | Leyne, Sean |
Post date | 2013-03-16T19:25:09Z |
Dan,
The local application (called the client, Tier 1) would connect to a remote application server (Tier 2) via the internet, which would be responsible for connecting to the database engine (Tier 3).
This is a common design/application development pattern, but it is one that will require changes to your application.
Sean
> --- In firebird-support@yahoogroups.com, Mark Rotteveel <mark@...>That model can work, but it requires a 3 tier application design.
> wrote:
> > The Firebird wire protocol does not perform well over higher latency
> > connections, like over the internet.
> >
> > Also, are you implying that your server is directly open and available
> > on the internet? You might want to consider only allowing web-traffic
> > and SSH and closing off everything else.
> >
> > You could consider connecting with SSH and executing the script locally.
>
> Thanks, Mark. The thing is, the use of the script was just a test - I have a
> commercial app which is an installed Windows app, that uses Firebird
> (either embedded or a server version) for local or LAN access to its DB. I was
> thinking of offering an option where I could have Firebird and the users' DBs
> on my server, with them still installing the app on their computers. But if
> what you say is true, I need to instead be thinking of a real web app, or
> using a different DB that does perform better over the Internet. (Any
> suggestions?)
The local application (called the client, Tier 1) would connect to a remote application server (Tier 2) via the internet, which would be responsible for connecting to the database engine (Tier 3).
This is a common design/application development pattern, but it is one that will require changes to your application.
Sean