STRUGGLING WITH EXPORTING NOTES DATA TO SPREADSHEETS? NO MORE! Try IntelliPRINT, The world's leading Reporting, Dashboards, and Analysis solution for Notes & Domino
Don't spend unproductive time maintaining different versions of the same spreadsheet
Preserve data integrity and security in multi-user environments
Create reports in minutes INSIDE Notes
Get freedom from iterative report requests, deliver self-serve capabilities
Experience Reporting, Dashboards, and Analysis INSIDE Notes!
Sorry, I said I'd write this over a week ago. Don't the weeks fly by though. It seems I blink on Monday and then it's Friday. Oh, the treadmill of life.
My claim is that RIA technology is justified when the interaction requires it
In essence, as Ferdy noted, there isn't really any clear way to decide whether to use RIA or not. It all depends.
For those of you wondering what RIA is, it's Rich Internet Applications and is primarily Flex, but also things like Silverlight.
Once you fall for the lure of RIA it's all too easy to see how it could fit any problem and just use it for everything. That's bad.
Just as important as knowing when to use it is knowing when not to (which is the same thing I guess).
Don't use RIA if you don't need to.
Don't use RIA if you aren't sure the audience will always be able to.
Don't use RIA for a plain website just because you think it will make it look cooler.
Don't use RIA if you want the site to be reliably indexed by Google et al.
Sorry I can't offer anything more definitive. There just isn't a definitive guideline to follow. Working, as I do, alone, I have the luxury of making the call in most cases, so have never needed think about it to such a degree.
Mixing The Two
As we speak I'm working on a website that mixes both RIA and traditional web technologies. The site allows children of school-going age to create posters about their experience with the outdoors and nature. They can browse existing posters using a normal HTML-based website. If they want to make their own then they register and login using normal HTML forms and then up pops a Flex-based app in a new window.
I could probably have done the whole site in Flex, so that they browse entries, register and login via Flex too. I didn't need to though, so I didn't.
On the flip side I probably could have created a poster-making app in pure HTML. It would have been a nightmare of a job though, not been as nice a product and taken four times as long to do it. So I chose RIA.
We are just implementing ID vault, and there are still some accounts that have not been vaulted. Only way to tell is to actually open up the ID vault DB and look for that person or to go to the users client and check their security settings. It would be nice if in the person document there was an indication that the account has been vaulted. This would also be useful when we have technicians asking for the users physical id because they say it is not vaulted. We often discover they have typos in name or server.