A day in the life of 

loop:

    it takes 30 minutes to install IIS, then
    write a web service using VS 2005 and
    have it working

    it takes 3 days to install Apache, Tomcat,
    work out how Ant works, configure all the
    servers and write a web service using Java
    and have it working

    dilemma, CMS provides a native, mature,
    high performance Java API. also exposes
    that API via web services

    dilemma, writing a .NET thick client to
    replace part of the front end of said CMS.
    limited to using web services, or .NET
    Remoting or some other MS proprietary
    technology to communicate with the CMS.
    the web services API is low level leading
    to a large number of calls being sent to
    the SOAP server. performance takes a dive.
    solution; write a web service layer which
    wraps the native Java API provided by the
    CMS and expose "system" level functionality
    using a service oriented architecture.
    reduce the number of calls to web services,
    and use the local java libraries to talk
    to the CMS

jmp loop

never_get_here:

    Yaasssss you bitches!!!

jmp never_get_here