It was definitely 'mapped' into our world. There are steps in the API that logically would never be used 'standalone', but as the underlying process broke the functions out as the underlying API did -- for example -- the PrepareXML must be followed by OpenXML -- why show that to us developers?!? We should have received a "PrepareAndOpen" function call instead. I mean, I will never do a PrepareXML that is not immediately followed by an OpenXML. It was a literal implementation of the underlying requirements without any thought to the 'target user'. Anyway, that kind of design ugliness was what said 'checkbox item' over 'well thought out' or 'implemented for real users' to me. I voiced this the first time I went through the process -- my point was that all parts of the systems handles that kind of 'allocation of memory' without it having to be explicitly executed. The XML add-on is the most "C" like stuff ever presented to us to use in BASIC! <g>
So I'm in the camp that "I like that it is built in to UniData, but it really was a cheesy (and maybe even inconsiderate) job on the design and implementation" That was my take anyway! -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Steve Romanow Sent: Tuesday, October 26, 2010 6:36 PM To: U2 Users List Subject: Re: [U2] Building XML using the UV XDOM API functions Compared to something like lxml it seems rather clumsy and unmaintained. On 10/26/10, Gregor Scott <[email protected]> wrote: > I actually like the XML handling built into UV. I have always been a > believer in using the intrinsic facilities of the database where possible to > maximise the performance of the process being automated. The XDOM API is a > good example of this, and is a good fit for our requirements. > My biggest issue is with the poor state of the documentation. It does not > allow me to easily obtain a good level of competency, which I think is > needed to feel like I can be productive with a tool, and to feel that the > tool is worth using. > Once I got past the documentation and did a lot of testing, and raising > cases with Rocket Software (the guys here in Australia should now know their > XDOM backwards!), I have a much clearer understanding of what is possible > and what the limitations are. > > Which is why I created the blog and started adding entries for various > aspects of the XDOM that were not obvious from the documentation. I just > hope it helps others get a handle on the XDOM API a bit quicker than I did. > It might also allow others to better evaluate the XDOM API as a valid > toolset, rather than discount it out of hand due to FUD, or marketing > pressures. > > Gregor > > -----Original Message----- > From: [email protected] > [mailto:[email protected]] On Behalf Of Tony Gravagno > Sent: Tuesday, 26 October 2010 3:35 PM > To: [email protected] > Subject: Re: [U2] Building XML using the UV XDOM API functions > > Gregor, your comments serve as a testimonial to support my > position against using many of these vendor-supplied toolkits. > Some of them are OK, but many not. People insist on the DBMS > vendors building stuff for them, but then we get the mess that > you've described. For this reason I continue to recommend at > least consideration for integration with tools that are outside > of the DBMS. DBMS vendors should be focusing on making superior > databases, not XML, web services, or a lot of this other fluff. > People in the open source and commercial markets spend a great > deal of time focused on these things, and because of this, their > offerings are often much better. So take a look around and weigh > other offerings against the built-in functionality. It would be > nice to see people here comparing more toolkits - it might save > others from feeling like they're stuck with whatever is provided > by the DBMS vendors. > > T > > _______________________________________________ > U2-Users mailing list > [email protected] > http://listserver.u2ug.org/mailman/listinfo/u2-users > -- > Message protected by DealerGuard: e-mail anti-virus, anti-spam and content > filtering. > http://www.pentanasolutions.com > > Click here to report this message as spam: > https://login.mailguard.com.au/report/1AYrw4K3L1/76hLrBplQLdEzGQ20K2ljp/0 > > > This email and any attachments to it are confidential. > You must not use, disclose or act on the email if you are not the intended > recipient. Liability limited by a scheme approved under Professional > Standards Legislation. > _______________________________________________ > U2-Users mailing list > [email protected] > http://listserver.u2ug.org/mailman/listinfo/u2-users > -- Sent from my mobile device _______________________________________________ U2-Users mailing list [email protected] http://listserver.u2ug.org/mailman/listinfo/u2-users _______________________________________________ U2-Users mailing list [email protected] http://listserver.u2ug.org/mailman/listinfo/u2-users
