| Subject | Re: [ib-support] Firebird works. |
|---|---|
| Author | Helen Borrie |
| Post date | 2001-11-29T11:21:01Z |
At 10:19 AM 29-11-01 +0000, you wrote:
you ARE talking about LIBS here, right? If so, it's contrary to what your user support people would say - and I'm talking here not about 16-bit v.4 but 32-bit v.4.x and 5.x.
The understanding I had was that the IB licensing that installed from the Delphi disks limited the number of LIBS connections to four. The slowness of LIBS as compared with a localhost or remote connection was demonstrable. The flakiness of LIBS when threading is involved (e.g. when *legally* using unlimited multiple LIBS threads from a web application) didn't really come to the surface until open source removed the licensing limitations.
Charlie Caro attributed the LIBS blow-ups with multiple threads to the fact that, with local connections, the client and the server share the same inter-process communication space. IOW, additional threads overwrite and corrupt one another's messages, or try to and cause GPFs. He commented to the effect that LIBS was designed that way and it wasn't likely to be fixed because it wasn't broke. My inference: now I understood why IB support would say "LIBS wasn't intended for deployment".
regards,
Helen
All for Open and Open for All
InterBase Developer Initiative ยท http://www.interbase2000.org
_______________________________________________________
> > > Helen wrote,Paul,
> > > local InterBase server was patched into the Windows distros by Borland
> > > as a convenience to developers. It was never intended to be deployed.
>
>Only the original 16bit 4.0 kit was a "patched" build that was never meant
>to be deployed, only used for development.
>All builds from then on were intended to be development / deployment kits.
>There was no difference in the builds that were provided in the 32bit
>environment for Borlands Development tools, and the ones that were available
>for deployment. They were exactly the same.
you ARE talking about LIBS here, right? If so, it's contrary to what your user support people would say - and I'm talking here not about 16-bit v.4 but 32-bit v.4.x and 5.x.
The understanding I had was that the IB licensing that installed from the Delphi disks limited the number of LIBS connections to four. The slowness of LIBS as compared with a localhost or remote connection was demonstrable. The flakiness of LIBS when threading is involved (e.g. when *legally* using unlimited multiple LIBS threads from a web application) didn't really come to the surface until open source removed the licensing limitations.
Charlie Caro attributed the LIBS blow-ups with multiple threads to the fact that, with local connections, the client and the server share the same inter-process communication space. IOW, additional threads overwrite and corrupt one another's messages, or try to and cause GPFs. He commented to the effect that LIBS was designed that way and it wasn't likely to be fixed because it wasn't broke. My inference: now I understood why IB support would say "LIBS wasn't intended for deployment".
>The only difference, tended to be the license key :-)..when licensing was in effect, yes; once licensing was gone, the REAL differences surfaced and caused problems. Is this not the case?
regards,
Helen
All for Open and Open for All
InterBase Developer Initiative ยท http://www.interbase2000.org
_______________________________________________________