Nah, I think Mike Tyson is not techie enough to kick into this conversation and get upset.
Sorry to disappoint! Maybe next time. Haha R On 6/18/02 2:40 PM, "Thomas Ferguson" <[EMAIL PROTECTED]> wrote: > does this mean its over???? > > Nobody bit anyones ear... > > Such a great opportunity too... > > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]]On Behalf Of Robert S. Sfeir > Sent: Tuesday, June 18, 2002 2:38 PM > To: Multiple recipients of list witango-talk > Subject: Re: Witango-Talk: XML is change > > > You have too. Glad to see this didn't degenerate into a flame war ;-) > > Glad to see there is still a sense of normalcy after being absent for a > while. > > R > > On 6/18/02 2:00 PM, "Scott Cadillac" <[EMAIL PROTECTED]> > wrote: > >> Thank you Robert, >> >> You've made some excellent points here. >> >> Your insight is valuable. Cheers.... >> >> >> ----- Original Message ----- >> From: "Robert S. Sfeir" <[EMAIL PROTECTED]> >> To: "Multiple recipients of list witango-talk" <[EMAIL PROTECTED]> >> Sent: Tuesday, June 18, 2002 10:38 AM >> Subject: Re: Witango-Talk: XML is change >> >> >>> On 6/18/02 1:06 PM, "Scott Cadillac" >> <[EMAIL PROTECTED]> >>> wrote: >>> >>>> Hi Robert, >>>> >>>>>> 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. >>>> >>>> But I'm not using Java. I use Witango. So, you've added to my point - >> thank >>>> you:-) >>> >>> Actually I was making the point that though you might be using WiTango, >> you >>> can STILL use java. Last I checked JavaBeans was supported and alive in >>> WiTango and it all worked really well. So there is no reason why the 2 >>> could not be combined since a JavaBean can handle the processing of the >> XML >>> to XSLT also. Further you seem to forget about the JAS server which also >>> allows you to do lots of stuff like that. >>> >>>> >>>> >>>>>> 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. >>>> >>>> I support Standards too, but lets face it - they take too long to >> finalize! >>>> So that funky stuff is called innovation while waiting for everyone else >> to >>>> play catch-up. >>>> >>>> Sorry - just teasing :-) But the wait for standards can take so long >> that >>>> they border on more harm than good. >>> >>> True, no argument there, they DO take sometimes TOO long to get going, my >>> position on that is start using them and change them if and when you need >> to >>> and the standard is out. Usually things are not that far off. >>> >>>> >>>> >>>>>> >>>>>> 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. >>>> >>>> Here's an excerpt from today's www.byte.com Java Resources section. >>>> >>>> (Portable at the byte code level, but only to the extent that different >>>> implementations of the Java VM are compatible with each other. The >> promise >>>> is "Write once, run anywhere." The reality is "Write once, test >>>> everywhere." ) >>> >>> Yeah their has been a lot of that... But please don't confuse this issue >>> with GUI issues, and by GUI I mean Swing/AWT issues which carry from >>> platform to platform. I have yet to have a problem with server side >>> implementations of Java where I couldn't take a servlet and just move it >> to >>> another server, just like I can with WiTango-based applications. I move >> my >>> javabeans from any platform TO any platform that WiTango supports and I >>> never ever have to write anything twice. >>> >>> >>> 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 >>> >>> >> >> ________________________________________________________________________ >> TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED] >> with unsubscribe witango-talk in the message body >> > > 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 > > ________________________________________________________________________ > TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED] > with unsubscribe witango-talk in the message body > 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
