Remoting vs Indigo taking *nix and Mono into account


I'm designing a distributed system (actually redesiging DCOM app).  Planning to use Remoting but Indigo is on the horizon so have been taking a look at that.   Ideally, I'd like the same code base for Unix/Linux.  I understand Remoting should theoretically work on Mono.  I've been told Indigo will never be ported to Mono because MS isn't going to license the technology to allow it.   If Indigo isn't going to be there, I'll probably stay behind with Remoting. 

any comments

Dave


Answer this question

Remoting vs Indigo taking *nix and Mono into account

  • mz1derful

    Thanks Doug.  Why did you bother typing that reply   Ya, I know MS doesn't develop Mono but it has control over the technology.  Here's a little tidbit from mono-devel-list.

    "... I joined the development team of a project that was then called "MonoIndigo". This was designed to be a port of Microsoft's Indigo framework (now known as the Windows Communication Foundation). As many of you know, Microsoft made it clear that any kind of direct port of Indigo was not going to be accepted, and would be in breach of IP regulations. Likewise, the same would apply for Avalon (now known as the Windows Presentation Foundation I believe).

    The main aim of that project, was to EXTEND Indigo's appeal, by making the same code, unchanged, run on any platform that Mono run's on.

    Seeing as this can no longer be the case, the project was changed, re-named, and is no longer a direct port of Indigo. ..."

    Would have been nice. 

    FYI



  • HasanTariq

    My concern is *nix machines being servers.  Clients are more likely to be Windows machines.

    If Indigo is not going to be availalble on *nix w/ Mono then I can't use it.   I'm assuming the lack of an answer to this question means no Indigo support is ever likely to be in Mono.

    Thanks,
    Dave



  • Sean Patzer

    We don't develop Mono.

    You should ping those folks and ask them what their plans are.

  • sqlplover

    I have heard about the general ban in IIS that some companies will apply.  I think there is something to be said for pushing back against this in light of IIS 6, which is significant change in terms of security over IIS 5.x. 

    Alternatively, Indigo will allows you to self-host or host in an NT Service and still support http using HTTP.SYS without the install of IIS.  This is a possible route for writing your service using Indigo and having ASMX clients on Windows and *nix.

    I'm not sure about Vista (the client OS) having IIS out-of-the-box or seperate install but my understanding is that the server version would be similar to Win2k3 Server and require adding server role to get IIS.  Vista doesn't need IIS unless you are planning on hosting on the client OS and want to use ASMX versus Indigo.

    HTH,

    Matt

  • Sinc at devBiz

    If *nix are the servers then the restriction on IIS shouldn't be an issue.  In that case, you could run ASMX web services on your *nix server using Mono and whatever web server you need to host ASMX on *nix and then use Indigo or ASMX Web Services on your Windows clients.  There is no need for IIS on the client for consuming ASMX Web Services.

    I don't know what the ultimate plan is for Mono and Indigo in the long run. 

    Thanks.

    Matt



  • Sue Hoegemeier

    Alternatively, you could consider ASMX web services.  This would get move your app into the world of service orientation, which is more in line with the general architectural direction for building distributed systems on the .NET Framework.  This would also get you an implementation that is interoperable with Indigo as well, which would allow you to provide a better migration path over time to Indigo should it be available on your target systems.  Additionally, this would allow you to build services on Indigo that would work with Windows and non-Windows clients offering potential benefits for taking advantage of the unified Indigo programming model.

    Matt Tavis
    Program Manager
    Microsoft Corporation

  • bjohns9959

    Matt, our dist app will utilize a cluster of compute servers.  Ideally, every capable box at a customer site could be a potential server.  I think web services would be a nice clean solution but then that would require IIS on each server.  This is a deployment headache.  There seems to be a hesitation on the part of customer IT depts to install IIS, let alone on a large number of machines.  I don't know why there seems to be this fear.  Maybe it's just a fear on the part of the end-user of their IT dept giving them grief.  In any case, it seems to be a road block.   Am I wrong

    Is IIS in Vista out-of-box or is it still a sep install    If MS is pushing web services for dist app, this seems like a necessity.

    Thanks for the reply,
    Dave


  • Remoting vs Indigo taking *nix and Mono into account