| Subject | Re: [ib-support] Connecting to a remote server using phone line |
|---|---|
| Author | Jason Chapman (JAC2) |
| Post date | 2002-02-01T11:08:38Z |
�agatay,
I use replication over a telphone line at 33Kbps, it works OK, but it canbe
a little slow and doesn't really use all of the bandwidth available. My
system probably replicates a record per second, but mileage varies based on
record width etc.
Replication is purely the best solution as your updates either happen and
commit, or are still pending on the client. Although you do get the odd
problem with limbo transactions (another story).
I did some work for a company that had the staff in the field solution and
were considering the problem. They had multiple datasources they wanted to
update and they already had an e-mail infrastructure in place. I think they
were Oracle on the server, paradox on the client. I suggested:
1) ensure there is some mechainsm for handling contention.
2) When data that the user subscribes to on the server, fill a to-do log.
3) A process at the server end looks for to-do's, groups them together,
builds something like DML (inserts / updates / deletes), but more like an
INI file format so contention can be managed, DML is a little tricky to
parse to say "hey user, this is what I intend to do for you", plus the
datastructs weren't identical at each end - I fihured (and now I would use
XML), that having an independent transmission format would allow the client
SW to translate and update local info.
4) The server side robot zips the info up and sends this to the salesman as
an email, changing the extension to something that wil launch the client
side updater when double clicked.
4) salesman gets mail, double clicks attachment and auto updates system.
5) I advised that they had sequence numbers and the ability to resend etc.
Now my part was swanning in, giving advice, proof of concept and going away,
so I don't know how it panned out, but they were pleased as puch to leverage
existing communication mechanisms and not have toinvest in any new modem
pools etc.
Other bonuses were:
1) Ease of debug - the files were just zipped INI
2) Ease of difference in versions of server and client - Salesman has 2
versions ago, but you can write fileters server side to allow for backward
compat.
As I said, I would use XML now as it is such a robust standard, although
without zipping, may be wastefull in terms of how verbose it is.
my 2c
JAC.
"�agatay Tengiz" <tmd0307@...> wrote in message
news:DNEPLLFPOHPEDGIOCIIFCECACJAA.tmd0307@......
I use replication over a telphone line at 33Kbps, it works OK, but it canbe
a little slow and doesn't really use all of the bandwidth available. My
system probably replicates a record per second, but mileage varies based on
record width etc.
Replication is purely the best solution as your updates either happen and
commit, or are still pending on the client. Although you do get the odd
problem with limbo transactions (another story).
I did some work for a company that had the staff in the field solution and
were considering the problem. They had multiple datasources they wanted to
update and they already had an e-mail infrastructure in place. I think they
were Oracle on the server, paradox on the client. I suggested:
1) ensure there is some mechainsm for handling contention.
2) When data that the user subscribes to on the server, fill a to-do log.
3) A process at the server end looks for to-do's, groups them together,
builds something like DML (inserts / updates / deletes), but more like an
INI file format so contention can be managed, DML is a little tricky to
parse to say "hey user, this is what I intend to do for you", plus the
datastructs weren't identical at each end - I fihured (and now I would use
XML), that having an independent transmission format would allow the client
SW to translate and update local info.
4) The server side robot zips the info up and sends this to the salesman as
an email, changing the extension to something that wil launch the client
side updater when double clicked.
4) salesman gets mail, double clicks attachment and auto updates system.
5) I advised that they had sequence numbers and the ability to resend etc.
Now my part was swanning in, giving advice, proof of concept and going away,
so I don't know how it panned out, but they were pleased as puch to leverage
existing communication mechanisms and not have toinvest in any new modem
pools etc.
Other bonuses were:
1) Ease of debug - the files were just zipped INI
2) Ease of difference in versions of server and client - Salesman has 2
versions ago, but you can write fileters server side to allow for backward
compat.
As I said, I would use XML now as it is such a robust standard, although
without zipping, may be wastefull in terms of how verbose it is.
my 2c
JAC.
"�agatay Tengiz" <tmd0307@...> wrote in message
news:DNEPLLFPOHPEDGIOCIIFCECACJAA.tmd0307@......
> Hi list,which
>
> How can I connect to a remote server using phone line for more explanation
> my scenario is something like that : My client computer dials a number
> is connected to server, server hangs up the line and my client computer
> connects to database.
>
> Is it possible, if so is there any documentation about this, if there is
> where I can find'em?
>
> In fact I really do not know if this is a pure FB realted question but I
> could not find anywhere else to ask.
>
> PS : I'm using D6, IBO, FB RC2 and my sever is on windows
>
> TIA,
>
> Best Regards
>
> Cagatay Tengiz
>
>
> _________________________________________________________
> Do You Yahoo!?
> Get your free @... address at http://mail.yahoo.com
>
>
>
> To unsubscribe from this group, send an email to:
> ib-support-unsubscribe@egroups.com
>
>
>
> Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
>
>
>