|
In my case I was seeing if XMLSERVICE was a possible valid replacement for the Client Access Drivers or the JT400 .Net Wrapper we built.
We wrapped JT400 into .Net about 7 years ago and it smokes and doesn't need CA/400.
XMLSERVICE works and seems pretty nice, however there are warnings on the YIPS site about using the XMLCGI in production apps.
This makes me wonder if it's worth pursuing or should I stay with the standard APIs.
Don't want to be forced to deploy Zend Server just to do database access.
Talk about overkill :-)
Regards,
Richard Schoen
RJS Software Systems Inc.
Where Information Meets Innovation
Document Management, Workflow, Report Delivery, Forms and Business Intelligence
Email: richard@xxxxxxxxxxxxxxx
Web Site: http://www.rjssoftware.com
Tel: (952) 736-5800
Fax: (952) 736-5801
Toll Free: (888) RJSSOFT
------------------------------
message: 2
date: Wed, 01 Aug 2012 15:26:53 -0400
from: Alan Seiden <alan@xxxxxxxxxxxxxx>
subject: Re: [WEB400] XMLSERVICE with .Net
Richard, good topic.
PHP users are using XMLSERVICE heavily because it is the back end of the new PHP toolkit. I even helped one customer call XMLSERVICE from a Linux cloud client.
Regarding .Net, I believe Craig Pelkie has an article coming out about using XMLSERVICE from .Net.
Jon Paris has been doing a presentation where he talks about using XMLSERVICE for customers, to demonstrate that program calls can be exposed as "instant" stored procedures and web services.
I'm interested to hear how people are using XMLSERVICE.
Alan
--
*Alan Seiden Consulting LLC*
PHP for IBM i Consultant and Advocate
Lead PHP Developer, new toolkit for IBM i Zend Framework certified contributor
Office: 201-447-2437 Cell: 201-248-4704
http://www.alanseiden.com | alan@xxxxxxxxxxxxxx
http://alanseiden.com/tips
http://twitter.com/alanseiden
As an Amazon Associate we earn from qualifying purchases.
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.