Yes, in a large environment.  But when you're presented with a client that
asks for ".net compliancy" then you shouldn't be thinking java.

Java and .NET and other languages can certainly work with each other, but if
you have the option then you're better off sticking to just one for a
project and if you're working for a client that is asking for a solution for
a single environment you should deliver a solution in that environment.
Even delivering a bd.net solution is questionable (fine as long as client
approves).  

Sam

> -----Original Message-----
> From: Guy Rish [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, July 27, 2004 1:32 PM
> To: CF-Talk
> Subject: RE: .net compliant (ot)
>
> Sam,
>
> I remember a time not really that long ago when people said
> that of tools
> like ColdFusion vs. Java - in '98 I was doing roadshows for an Allaire
> partner and people kept asking ColdFusion or NetDynamics.  
> People disagreed
> strongly with me when I told them that ColdFusion and Java could be
> cooperative platforms - then CF 4.5 rolled out.
> Guess what?
> If the tools start help the developer out (imagine that) -
> then Java and
> .NET can be cooperative platforms.
>
> In small shops it is simpler to pick one and stick with it -
> unless you want
> to use third-party tools that haven't moved over to your selected
> platform...  But in a larger enterprise it is seldom
> practical to expect
> that everything is either Java or .NET (or even one of those for that
> matter).  Frequently you have situations where This
> department uses Java and
> That department uses .NET and need to merge or share.
>
> rish
>
> -----Original Message-----
> From: Samuel R. Neff [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, July 27, 2004 12:18 PM
> To: CF-Talk
> Subject: RE: .net compliant (ot)
>
> Why would you need java components or java connectivity if
> you're running
> BD.NET, especially for a client that is asking for ".net
> compliancy"?  The
> whole point of BD.NET is to run in a pure .NET environment using .NET
> components and functionality.  
>
> Unless there is no other option, it's usually best to stick
> to pure Java or
> pure .NET and not mix them.
>
> Sam
>
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings] [Donations and Support]

Reply via email to