×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
The reason for the XML is just as you have stated, two different languages
and XML is supposed to be very portable. Also for me to learn something new
in the process. .NET seems to handle XML quite well so I wouldn't say that
there is overhead on that side. I could be transmitting up to hundreds of
fields of data back and forth (if it's a subfile). I figured XML is easiest
to work with realizing that.
--
Mike Wills
http://mikewills.info
P: (507) 933-0880 | Skype: koldark
On Tue, Dec 1, 2009 at 1:47 PM, Charles Wilt <charles.wilt@xxxxxxxxx> wrote:
XML is nice for exchanging data outside your company, or at least with
applications outside your control. But if you control both sides, XML
adds some overhead that's usually not needed. However, since you're
dealing with two platforms and two languages it may be worthwhile.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
