> -----Original Message-----
> From: news [mailto:[EMAIL PROTECTED] Behalf Of Vic
> Sent: 14 September 2004 14:48
> To: [EMAIL PROTECTED]
> Subject: Re: Advantages of J2EE w. Struts vs .NET ASP.NET
> 
> 
> Pilgrim, Peter wrote:
> > 
> > The trouble with RIA is that there is no universal defacto
> > browser technology. There are lots of interesting solutions
> > for rich functionality. My gut feeling it is gooing to take
> > a twentieth-first century equivalent of Netscape and Microsoft
> > to really push forward a next generation [XML/XSLT/ T(x)] browser
> > 
> > Where T(x) stands for some new technology.
> > Hint substitute T(x) for SVG, XUL, Flex, or whatever you
> > think it is going happen.
> > 
> 
> Hey Peter, I saw your post on TSS or RiA.
> Rich Internent Application, key word is *APPLICATION*. There is no 
> browser, that would make 2 sets of windowing API. Like iTunes is an 
> aplication.  Or Limewire is an application. It makes it 
> simpler and more 
> powerfull w/o browser, just use browser for launch. I think Java 
> WebStart is big, no such thing in .NET . (Java of course for cross 
> platform, how do I do a network launch w/ .NET on Mac?). Look 
> who owns 
> the browser standard. (IE of course, with all the plug in, so 
> .... lets 
> just  bypass it, nothing worse than coding JSP for IE)

RIA sounds like an advancement that I did four years ago before
Struts. It was an HTTP Tunnelling application with Java Plug-in
Swing Client communicating with a Servlet. Basically I built
a massive registry editor (JTree) and serialise MutableTreeNode
down the pipe to the applet, of which a selected or edited node
was sent back to the servlet. 

I guess it is, "How long is a piece of String?" nope let me
paraphrase "How thin is thin?" The RiA can be Swing / 
Webstart, complete and very self-contained application. 
But it could be a build as as application running on someone
else's framework, such as a browser.

If I was to redo my application I would do it with Struts still
to at least to divorce myself from Servlet code. In fact it is
the sort of stuff that lends itself to web services or Struts 2.0
Jericho, where we have abstracted away the HttpServletRequest
etc.

The other thing about RiA I can think of, who standardises
the user interface. Surely if you use an application then
you cannot use it on a WAP/Cellphone device, whereis the
XML and XSLT should allow you do this for you.

> As far as development enviroment, if you compare Sun's JCP 
> Java ... we 
> lose, we lose big:
> http://theserverside.com/news/thread.tss?thread_id=28695
> (See the GridBag demo)
> 
> But if you include O/S, like JGoodies (iBatis, etc.) ... we win. I do 
> think there will be O/S for .NET (like Apache is porting, Ant is 
> porting, iBatis is porting.... so it will be closer. More of 
> a tanget: I 
> think Unix is MUCH more stable than viruses on Windoze. Just 
> check out 
> Redhat Fedora. So ... for heavy lifting, Linux. For departmental, 
> WinAntiVirusCitySlowPoke)
> 
> Anyway, I think future is iTunes-like-applications concept (with 
> "distributed web services" arcitecture), I will have a sample next 
> month, posted on my site only.
> 
> 
> .V
> boardVU.com
> 




--
Peter Pilgrim
Operations/IT - Credit Suisse First Boston, 
10 South Colonnade, London E14 4QJ, United Kingdom
Tel: +44 (0)207 883 4447

==============================================================================
This message is for the sole use of the intended recipient. If you received
this message in error please delete it and notify us. If this message was
misdirected, CSFB does not waive any confidentiality or privilege. CSFB
retains and monitors electronic communications sent through its network.
Instructions transmitted over this system are not binding on CSFB until they
are confirmed by us. Message transmission is not guaranteed to be secure.
==============================================================================


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to