On 6/18/02 12:02 PM, "Scott Cadillac" <[EMAIL PROTECTED]>
wrote:
> Hi Robert,
>
> Please see my replies below...
> ----- Original Message -----
> From: "Robert S. Sfeir" <[EMAIL PROTECTED]>
> To: "Multiple recipients of list witango-talk" <[EMAIL PROTECTED]>
> Sent: Tuesday, June 18, 2002 3:43 AM
> Subject: Re: Witango-Talk: XML is change (was: IE browser share now 93%
> in2002 (Off topic news))
>
>
>> Just curious about a couple if things:
>>
>> I can see why you might want to use XML only, but if you wanted browser
>> compatibility why not use XSLT for data transformation to HTML to all
>> browsers? It's just a matter of changing a template when you want to
>> display data differently, something that takes just as long as designing a
>> new HTML page really.
>
> You've hit the nail on the head! All in good time of course.
>
> Much like the frustration many have vented about client-side JavaScript
> being inconsistant across the different flavours of browsers - client-side
> XSLT is also not consistant or even exist in some browsers.
AHA, But here is where I see it differently. The beauty of XSL:T is that
you can use a servlet to make the changes for your call. Therefore the
processing is done outside the browser. FURTHER, you can pass the TYPE of
browser to the servlet and call the appropriate XSLT template all
preprocessed back to the client exactly like the client expects it. The way
I see is that you can have say 5 templates (one for each browser) which will
represent your HTML appropriately based on each web client you use. Better
than having tons of logic or limiting yourself to the lowest common
denominator.
>
> Reliable and consistant server-side XSLT for all platforms has not arrived
> yet in my opinion. Plus I'm waiting for pre-emptive threading for use with
> Witango and to see what XSL support may be available to us in the future.
If you use Java, I can't agree with that comment. JAXP was just released
recently into final production, so has the Web Services standards for Java.
The threading model is also a non issue with Java.
> As far as client-side XSLT goes - I view the arrival of Mozilla 1.0 to be an
> important one. Mozilla's gold status may not noticably influence the mighty
> gods of MSIE, but I think it will sway all the other browser makers to get
> their ducks in a row by measuring their product capabilities against
> Mozilla's performance. Mozilla is a serious competitor - not to MSIE, but
> all the other browsers.
Yep, yet another reason why I don't believe in MS stuff, I have to see them
implement a standard from A-Z without adding more funky stuff on their own.
>
> Like developers used to say about Java - I only want to write my XML once
> and deploy it across many platforms :-)
What do you mean? We STILL say that. Hence my opinion in the first
paragraph.
>
> In the meantime - I'm testing, learning and planning. I'll write articles as
> I go, when I can.
Test, learning and planning... The most fun part of being an engineer.
(Sorry I snipped out the whole thread this email was getting big)
R
--
Robert S. Sfeir
Senior Java Engineer
NIH/CIT/DECA
e:[EMAIL PROTECTED]
v:1.301.594.2900
f:1.301.480.3232
________________________________________________________________________
TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED]
with unsubscribe witango-talk in the message body
