Hi Roman,

Breifly my reasoning here was just that I wanted to avoid causing the user
to have to import from the gds interface package. For example - FBManager is
as far as I'm aware an API class - that is the user may import and reference
this class from there application. If a GDSType class in the gds package
where used everywhere then if the user wanted to set the driver type for
FBManager they would have to reference a class from the gds package - which
perhaps they should remain unaware of.

This was my reasoning. I would be very interested in your opinion on this.
Perhaps it would be better to just have a single class - but I would assume
that this class would need to be referenced by the user for some things.

Thanks
Ryan

-----Original Message-----
From: Roman Rokytskyy [mailto:rrokytskyy@...]
Sent: 19 August 2003 20:59
To: Firebird-Java@yahoogroups.com
Subject: [Firebird-Java] To Ryan


Hi Ryan,

It seems that my Yahoo account have problems delivering emails. Here's
my original email:

------------

Hi,

I'm continue my refactoring quest. Now I'm thinking about defining a
standalone class org.firebirdsql.gds.GDSType and reference it in all
other classes instead of having one defined in GDSFactory, one in
FBManagedConnectionFactory (and I think there's one in FBManager).
What do you think?

Thanks!
Roman Rokytskyy

------------------

Roman



To unsubscribe from this group, send an email to:
Firebird-Java-unsubscribe@yahoogroups.com



Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/