hi
On 7/26/06, Girish Venkatachalam <girish1729@xxxxxxxxx> wrote:
--- Venkatraman S <blizzard_venkat@xxxxxxxxxxx> wrote:
Hi,
I was thinking about the recent hype-hoopla w.r.t
Web services. JAVA, XML, WSDL , SOAP, UDDI etc
terminologies have been thrown around like
volleyballs in a beach. I was just trying to find an
analogy between RoR and the web services - in the
sense, what constitutes a service as a web-service ,
as such? I do not have much understanding of the
said concepts and would like to know more.
AFAIK Ajax is hot in Silicon Valley. Gmail and google
maps are good examples. Asynchronous XML + Javascript.
SOAP though originally from M$ seems to have good wide
spread use by folks including google.
Ajax programming is hard; so I believe it has
potential ; also it is cool as it gives an excellent
end user experience hitherto unimaginable. Dynamic
updation of web pages and background fetch enable user
not to perceive the network latency as pages are
fetched asynchronously. Much before the user thinks of
clicking at them.
Also the "applet" concept which failed works *very*
well with Ajax. The browser takes a good part of
processing onto itself.
This deadly combo makes for powerful ammunition with
which web developers can design the next incarnation
of Internet and browser centric applications.
Today the browser by virtue of flash and other things
is able to play video perfectly, even under linux. I
envisage a future in which the browser becomes a one
stop app for everything.
Also Ajax forms a very important building block for
Web 2.0 (which is again hype).
I know nothing other than expansions for the other
terms you mentioned. :-)
XML also was big hype, but folks compare it with ASN.1
and I think it has not delivered on its promise though
it is a powerful concept. XML/SGML seems to be popular
with DocBook and other document preparation tasks.
Also XML config files and information exchanges;i.e,
XML based protocols like SOAP are popular. But I think
sometimes XML is an overkill as it kills the
efficiency of binary protocols and adds too much
overhead as opposed to simple text based protocols
like SMTP, FTP or HTTP...
Bear with me if I digressed a bit. Also most of the
stuff are my opinions and not facts; hence they might
be wrong. Please correct me if you feel like...
HTH,
Girish
Regards,
vEnkAt
