Aaron wrote: > I agree with the sentiment, but using javascript in the manner that we > are discussing has allowed me to mimic much of the functionnality of > traditional clients over the web.
I understand this, and I agree that as designers, we're not always at liberty to say "Yes" or "No" to a customer's requests. It wasn't my objective to question your design, just to throw out a general note of caution for those using JavaScript for more than Web-UI enhancement. IMHO, there are ways around the mimicked MVC design requirement, and that a refactoring of the user interface to a web-centric model can be sufficient in many cases. The fewer requirements you place upon the browser, the fewer problems you have at the browser level. This is true whether it is an Intranet or Internet web-application. The downside is, of course, retraining the end-user to the new paradigm and making sure server and network performance is up to snuff. On a related note, I see this general sentiment of caution applying to the use of forms and hidden data to drive web applications rather than session data. I dread the day that I have to start supporting the internal Perl project we have at work. *shiver* If that day happens, there'll be some major changes to the session handler. (*rip, tear, replace, grin*) ;-) Good luck on the project! -- Chad Walstrom <[EMAIL PROTECTED]> http://www.wookimus.net/ assert(expired(knowledge)); /* core dump */ ------------------------------------------------------- This SF.net email is sponsored by: Etnus, makers of TotalView, The debugger for complex code. Debugging C/C++ programs can leave you feeling lost and disoriented. TotalView can help you find your way. Available on major UNIX and Linux platforms. Try it free. www.etnus.com _______________________________________________ Webware-discuss mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/webware-discuss
