Yes, there is a strong feeling in many places (including here) that Macromedia
is not focusing on ColdFusion as much as they should. This is seen in at least
one major deal dropped because they were not willing to bend any on the pricing.
That is besides the point. I'm just not understanding what your saying here.
"not necessary to wait for a web page to be submitted before getting feedback on
the entry to a data field"
This sounds like client side validation which means _javascript_. CF not only has
this but has easy hooks for building more in. Anyway, the point is that this is
NOT .net technology.

> This was a extra argument provided outside of the original comparison
document.
>
> Another reason Wyndgate said they are going to use .NET is that it is not
necessary to wait for a web page to be submitted before getting feedback on the
entry to a data field.  With .NET the validity of the entry can be checked
without submitting a web page to the browser.  This was their main point on why
they were going with .NET.  The other point was that they felt the Cold Fusion
technology was not the focus of Macromedia, the flashy parts of web programming
were their primary focus.
>
>
> To those who have waded through all of this, thank you a third time.
>
> --------------
> Ian Skinner
> Web Programmer
> BloodSource
> www.BloodSource.org
> Sacramento, CA
>
> "C code. C code run. Run code run. Please!"
>      - Cynthia Dunning
>
>
>
>
>
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]

Reply via email to