I'm interested in building some web services that can be used both by external web browsers, but also by internal SOAP clients. The architecture I see is a web server talking to an independent database/file system entity, with local developers able to also write scripts that will interact with the entity. Essentially the function is an advanced ftp site.
With regard to security, I'm wondering how SOAP takes care of authentication and authorization. I read the local articles SOAP::Transport::TCP connection problems, troubles writing mod_soap clients and SOAP::Lite, then went further afield and found this article about authentication under SOAP UDDI. Google also found this article on SOAP extensions which looks promising if only it weren't almost five years old. This code sample also looked useful, even if it is in Java.
I like the idea of using SOAP -- does anyone here have other technology suggestions?
Alex / talexb / Toronto
"Groklaw is the open-source mentality applied to legal research" ~ Linus Torvalds
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|
