Thank you Niall,

A very interesting perspective from someone so fresh to Witango - with many
powerful points in our favor given your years with ASP. By the way, we try
not to call Witango by it's former name anymore - an inside joke from the
recent Conference, plus we're looking to a whole new future not available
under the former owners of the product :-)

Here's a bit of information and a question.

Yes, you can assign your Witango database Actions with Dynamic Datasource
Variables (from an include or TCF) for when you need to change DSN
connection information at a later time. Or even if you want to run one set
of TAFs and TCFs in a multi-Domain environment. Here's a link with some
information on how to do this.

http://xml-extra.net/webpage.xmlx?node=41

Question, why do you list "Ports to three web servers (APACHE, MAC, IIS)"
as a Con?

In fact Witango also runs on Netscape Servers and can run on Linux and
Solaris as well as Mac and Windows. I think this is a Pro.

Welcome aboard buddy. Cheers....


Scott Cadillac
http://xml-extra.net
[EMAIL PROTECTED]

VP, Research and Development
Plus International Corp.
604-460-1843
[EMAIL PROTECTED]
http://www.plusinternational.com

Vancouver, BC, Canada

Does your company have an Enterprise Information Portal? Check out Salsa at
www.plusinternational.com/flash/salsa.htm

----- Original Message -----
From: "Niall Merrigan" <[EMAIL PROTECTED]>
To: "Multiple recipients of list witango-talk" <[EMAIL PROTECTED]>
Sent: Friday, June 21, 2002 3:18 PM
Subject: Witango-Talk: RE: Tango / ASP Death Match


> <SNIP>
>
> OK guys here is where i might come into my own
>
> I am an ASP programmer by design, I have been programming in ASP for
close
> to four years.  I think I have been coding in Tango for 4 weeks at most
>
> Here as what I found the pluses and minuses for both technologies
>
> For ASP:
>
> 1. Ships FREE with IIS
> 2. Native instruction
> 3. Huge developer base (VB, VBA, VBS programmers amd JavaScript)
> 4. BIG ONE FOR ME: Can include the DSN as an include file  (please dont
> flame if you can do this in tango ...just show me)
> 5. Can be coded without using specialised editors
>
> For Tango
>
> 1. Bloody quick development (RAD++)
> 2. Nice design interface
> 3. Fairly easy to learn if you have done previous server side development
> 4. Brilliant COM+ support
>
>
>
> Cons ASP
>
> 1. Known vunerabilities (translatef bug etc)
> 2. Runs on IIS
> 3. Can be messy if you mix languages (JScript and VBScript)
> 4. Portability an issue (needc third party plugins)
> 5. Slower Dev time (from code to ship)
>
> Cons Tango
>
> 1. Not as wide a user base
> 2. Runs on top IIS
> 3. Added cost (Buy Dev + App Server)
> 4. Ports to three web servers (APACHE, MAC, IIS)
> 5. Hard to code without Tango editor
>
>
> Now I have quite easily managed to integrate the two languages (running
> from asp to tango and back again).
>
> Now to put a few points to rest ... ASP can run on Apache (via Chillisoft
> ChilliASP and ChilliSpice (CDONTS support) this will also run ASP on
> Solaris)
>
> As for scalable .. its six of one, half dozen of another.  Portability is
> virtually the same (unless you change DSNs and then its a bit of a
> nightmare Tango side)
>
> I am not too sure of execution times or server times when running either
> lanague on simliar type apps
>
> But I will put it this way .. for your ASP programmers this will be
> another language they can learn (something to put on their CV!). I am
> managing to do it, even if it takes a little shift in my mind-set
>
> It seems futile to re-invent the wheel when the app is developed. You
> might be in an ideal situation because both type of developers will be
> able to give each other ideas
>
> Just my 0.02c (go Euro!)
>
>
> Regards
>
> Niall
>
>
>
>
> --
> Niall Merrigan
>
>
>
>
>
>
>
> ________________________________________________________________________
> 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

Reply via email to