Subject | Re: [IB-Java] Re: Dying connections with interclient |
---|---|
Author | David Jencks |
Post date | 2001-04-18T12:59:35Z |
Hi,
I think you start by figuring out the Firebird C client to server
communication protocol and writing a java client using it. You can then
figure out how to make the jdbc calls map to Firebird api calls (this is
much of what interserver does). Then you can figure out a way to handle
the DatabaseMetaData stuff (this is most of the rest of what interserver
does).
Some comments:
1. In my opinion, XAResource support is essential, indeed the main reason
to undertake this work. (the other thing interserver does is hide Firebirds
transaction capabilities and make XA support difficult.)
2. With an eye to the near future, any driver should include JCA support.
I'm not 100% sure what we want to end up with, whether XADatasource support
is essential, I think a Resource Adapter is more important. There is at
least one wrapper available (blackbox-tx example from sun) but we may be
able to do better by building it all ourselves..
3. My opinion is that the DatabaseMetadata calls should be implemented by
adding stored procedures wrapping the necessary system table queries to
every database we connect to. The java driver can then simply call these
sps with appropriate parameters. I'm not quite sure how to assure that the
sp's get into every database. Is it appropriate to add them to base
Firebird, even installations that aren't connecting from java? Otherwise
an installation step will be necessary... not so much fun..
I am quite interested in this (in fact I suggested the idea eliminating
interserver in this way), I may be able to work on it myself soon. Please
let me know if you make some progress on this.
Thanks
David Jencks
I think you start by figuring out the Firebird C client to server
communication protocol and writing a java client using it. You can then
figure out how to make the jdbc calls map to Firebird api calls (this is
much of what interserver does). Then you can figure out a way to handle
the DatabaseMetaData stuff (this is most of the rest of what interserver
does).
Some comments:
1. In my opinion, XAResource support is essential, indeed the main reason
to undertake this work. (the other thing interserver does is hide Firebirds
transaction capabilities and make XA support difficult.)
2. With an eye to the near future, any driver should include JCA support.
I'm not 100% sure what we want to end up with, whether XADatasource support
is essential, I think a Resource Adapter is more important. There is at
least one wrapper available (blackbox-tx example from sun) but we may be
able to do better by building it all ourselves..
3. My opinion is that the DatabaseMetadata calls should be implemented by
adding stored procedures wrapping the necessary system table queries to
every database we connect to. The java driver can then simply call these
sps with appropriate parameters. I'm not quite sure how to assure that the
sp's get into every database. Is it appropriate to add them to base
Firebird, even installations that aren't connecting from java? Otherwise
an installation step will be necessary... not so much fun..
I am quite interested in this (in fact I suggested the idea eliminating
interserver in this way), I may be able to work on it myself soon. Please
let me know if you make some progress on this.
Thanks
David Jencks
On 2001.04.18 02:57:33 -0400 Ola Samuelson wrote:
> What would typically be involved in eliminating interserver completely?
> This sounds more sane than debugging it. Or?
>
> Are there any major difficulites in doing the remote requests directly
> from interclient? I realize it may take some effort but it might be worth
> it.
>
> Could someone give me a clue where one would start?
>
>
> //OLAS
>
>
> Ken Richard wrote:
>
> > And you are still using interserver? I thought you would have written
> the
> > jni wrappers for that old odbc code you had around by now.
> >
> > -----Original Message-----
> > From: Jim Starkey [mailto:jas@...]
> > Sent: Tuesday, April 17, 2001 4:14 PM
> > To: IB-Java@yahoogroups.com
> > Subject: Re: [IB-Java] Re: Dying connections with interclient
> >
> > Ah, yes, did I mention that a Netfrastructure post-commit
> > trigger can now post the update to an Interbase database
> > via JDBC? Cool, huh?
> >
> > Jim Starkey
> >
> > To unsubscribe from this group, send an email to:
> > IB-Java-unsubscribe@egroups.com
> >
> > Your use of Yahoo! Groups is subject to
> http://docs.yahoo.com/info/terms/
> >
> >
> > To unsubscribe from this group, send an email to:
> > IB-Java-unsubscribe@egroups.com
> >
> >
> >
> > Your use of Yahoo! Groups is subject to
> http://docs.yahoo.com/info/terms/
>
>
>
> To unsubscribe from this group, send an email to:
> IB-Java-unsubscribe@egroups.com
>
>
>
> Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
>
>
>
>