×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
The transformations can easily be done on the server (I usually run in a
servlet container) and the XSLT's can be compiled so the transformation is
pretty cheap.
True, but then the scalability issue becomes even worse since it all resides
on the server at this point. Don't get me wrong, I think the approach can
work - I just think there are better (more CPU efficient) ways to do it.
I have a long time ago resigned to only ship finished HTML (in whatever
form) to the client, and only use Javascript through libraries.
What are your thoughts on only delivering JSON to the client concerning the
dynamic portion? In theory the static HTML+CSS+javascript files that
process/render the JSON would only have to be downloaded once.
Then you need to first define what "Efficient" means, and how to measure
it.
This isn't a scientific measurement/definition of efficient, but it is the
first thing that popped into my head when you asked.
Efficient, in one definition, is selecting a technology stack to communicate
with a UI that doesn't require you to upgrade your processing power.
For example, if a machine is at 30% utilization for CPU/memory then I
shouldn't have to upgrade machines simply because I chose to talk to a
different interface. Of course if the number of users increased
dramatically then that would be a valid reason for needing to upgrade - I am
more talking about the general user count to remain the same.
Aaron Bartell
http://mowyourlawn.com
http://mowyourlawn.com/blog/
midrange.com
