[jcifs] Re: Fw: SQL Server 6.5 and named pipes
David D. Kilzer
ddkilzer at kilzer.net
Sun Jul 18 21:54:54 GMT 2004
I don't think there will be any licensing issues per the recent
The jCIFS team (via Michael) said that they're willing to make changes
to jCIFS to help jTDS talk to SQL Server via named pipes. I also think
the jTDS team would prefer to distribute an unmodified jCIFS with their
JDBC driver in order to support named pipes.
And just to reiterate my goals:
1. Hack on jTDS and jCIFS to get them talking to SQL Server 6.5 via
2. Provide patches to both the jTDS and jCIFS development teams.
3. Work with both teams to clean up the patches so that they may be
integrated into each project, and so that jTDS may distribute an
unmodified jCIFS library to provide named pipe support.
Please correct me if I'm wrong, though!
On Sat, Jul 17, 2004 at 12:04:06PM -0500, Christopher R. Hertel wrote:
> Of note:
> Last time I spoke with the FSF's enforcement folk they told me that it is
> the copyright holder's responsibility to enforce the licencing terms.
> (This is why the FSF likes it if you hand copyright over to them--it lets
> them do their job.)
> As stated publicly on this list several times, our intent with jCIFS is
> that people should be able to write code that uses jCIFS as a library (or
> "toolkit"). Modifications to jCIFS itself should be available under the
> same license as jCIFS, but programs and utilities that simply use jCIFS
> are in two parts: the jCIFS part and the other part built on top of
> jCIFS. We're only claiming rights to the jCIFS part.
> Note: If FooBarInc modifies jCIFS and then uses the modified library as
> the basis for a new product, then the only folks who have a right
> to ask for source to the modified jCIFS library are those who have
> the FooBarInc product (per the LGPL).
> Chris -)-----
More information about the jcifs