Re: IBM i authentication and RESTful web service design

Richard,

I should apologize about using the term "SQL injection" so loosely. I know
the term has a negative connotation. My point was that one wouldn't want to
provide a "service" which enabled HTTP clients (SPAs, etc.) to send SQL
statements to a server for execution. Wouldn't you agree?

Of course ASP.NET applications send SQL statements to servers all the time
for execution, and there's nothing wrong with that. I couldn't help but
note the irony ;-)

Seriously, no offense intended in regards to your XMLSERVICE .Net Wrapper.
I view XMLSERVICE as a valuable resource. I admit to not having looked at
your .Net wrapper, but I have studied the PHP toolkit. Would it be a big
mistake for me to assume that your .Net interface is similar?

I don't recall saying anything recently about war in Iraq, ground water
contamination, or my general unhappiness. Is that your way of exaggerating
and fabricating a position for me?
,
Your viewing me as huffing and puffing anytime I think about .Net is
humorous. I admit to having issues with Microsoft products which I view as
competitive threats against IBM i. But I mostly believe that organizations
would be better served by migrating applications from Windows to IBM i.
Five years of professional experience dedicated to developing under Visual
... and deploying under Windows servers, should count for some credibility
;-)

What about 15 years experience developing hundreds of web applications
under IBM i? No?

In regards to educational opportunities at Microsoft Ignite; sorry, my
world does not revolve around Microsoft. But you already new that.
Hopefully that's okay on this list.