Why split it out over two network protocols?

If you are going write a SOAP layer you don't need to go over HTTP too to get the possibility of back-end-on-big-iron.

The GUI front-end needn't be .NET or Java. If you're happiest in perl, you could do a perl/Gtk2 (or perl/WxWindows or even perl/Tk) front-end. The first two options at least look pretty 'native' on Windows.

But if you're happiest doing GUI work as web pages, then you could do what you say. But then you could leave out the SOAP entirely. Just write a web app as you described.

Put a nice, clean abstraction layer in your code at that boundary and it will be fairly straightforward to SOAP-ify it later. And you'll even get to re-use your interface unit tests so that you know it's all working ;-)

So...my first choice might be zero network protocols (native client, with code on board). Do a decent model/view/controller split and then you'll have the option of putting in another controller/view for a web interface, talking to the same local model. Or the option of splitting off the backend over SOAP. But I'm not sure you need both.

In reply to Re: Desktop Application vs http://localhost by jbert
in thread Desktop Application vs http://localhost by perlmonkey2

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.