I'm tossing around ideas for the architecture for a new project. I'd like to keep the interface flexible, meaning I'd like to have the ability to use flash, html, "ajax",etc. I was thinking about creating all of the business logic as a set of web services. Any thoughts, pitfalls that I should avoid.
I really like the idea of separating out the interface from the business logic completely. I like the model-glue framework from a high level but I get an icky feeling when I have to start initializing the model with a config-bean from what should be the UI. Just thinking out loud I guess..... -- Marlon "A mulatto, an albino, a mosquito, my libido" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Logware (www.logware.us): a new and convenient web-based time tracking application. Start tracking and documenting hours spent on a project or with a client with Logware today. Try it for free with a 15 day trial account. http://www.houseoffusion.com/banners/view.cfm?bannerid=67 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:214111 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
