[Mono-devel-list] IBM DB2 and .NET (Stinger)

Rob.Tillie at Student.tUL.EDU Rob.Tillie at Student.tUL.EDU
Sat Nov 1 14:59:38 EST 2003


I'm wondering what IBM's reason is to support .NET... in any case, by
providing .NET support IBM confirms .NET's increasing market adoptance...
but I only can see I few reasons:

- Keep their DB2 customers who are switching to .NET
- Beginning to cover their ass as they are completely Java focused...

I began to think about the last option when I was reading today's issue of
SDTimes, on p.35 - p.36, which discuss Java's ongoing troubles...
IBM's competition would sure be great in the .NET world...

Anyone any opinions on this subject? Is IBM providing support for its
customers or for themselves?

Greetz,
-- Rob.

> -----Original Message-----
> From: Miguel de Icaza [mailto:miguel at ximian.com]
> Sent: Saturday, November 01, 2003 7:11 PM
> To: Sebastien Pouliot
> Cc: Daniel Morgan; Bryan Andrews; Rob.Tillie at Student.tUL.EDU; mono-devel-
> list at lists.ximian.com
> Subject: RE: [Mono-devel-list] IBM DB2 and .NET (Stinger)
> 
> Hello!
> 
> > Very interesting
> >
> > >- Take advantage of DB2's native stored procedure capability by
> developing
> > >on the Windows
> > >platform and deploying across all supported DB2 platforms
> >
> > How could they do that without a CLR for every DB2 platform ?
> >
> > Unless there are small print characters at the end of document ;-)
> 
> Funny.  I asked this exact same question at the `Embedding the CLR'
> panel during the PDC to the IBM guy (he was an invited expert in the
> panel).
> 
> They said that they had no plans at this point of supporting Mono on
> other platforms and mostly focused on getting the reliability on
> Windows for now, but that the option was not closed.  Something along
> those lines.
> 
> The IBM DB2 developer explained that DB2 does not host the CLR directly
> on the same process as the database.   It hosts it on a separate
> process, and they have some IPC mechanism to talk to it.  That allows
> them to host three scripting languages: Java, the CLR and their own,
> without having each one fighting for more control than they can provide.
> 
> I obviously would love to see IBM embed Mono as their offering on Unix,
> but it is early to tell.
> 
> Miguel.



More information about the Mono-devel-list mailing list