Craig, I would think twice about replacing synchronous communication
between web frontend and backend with async messaging. Probably this
will lead to major redesign of the system, besides you will have to
store local state somewhere in the web application (because messages
arrive asynchronously) and use polling at the client (javascript?) to
detect state changes. What good will it do to the application? For
sure it will complicate the web application and the browser javascript
code, it also might improve overall performance (or decrease it as
well) - of course if there was any performance problem at first. If
performance is the issue you should do some profiling to spot the
problem - probably the database access is the slowest and least
scalable part of the system, so using async messaging in the layers
above db will not change anything in query performance.
Rafal
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Rhino Tools Dev" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/rhino-tools-dev?hl=en
-~----------~----~----~----~------~----~------~--~---
