I guess one way to ask this is: if you guys(avalon developers) out
there working for a client who has a requirement to have a "very fast
service" implementation, would make "non proxiing" your service
component as one of your first choices to optimize your service.
no...let them buy more hardware first. Safety is important. Besides, enforcing the work interface / other stuff seperation keeps the code clean. It's often cheaper in the end to buy the hardware.
That said, proxying does cost roughly an order of magnitude in speed.
Another trick is to have proxying on all development/testing/debugging platforms. Then, during speed optimization and profiling, turn of proxying and see if it has a significant impact (with most apps, the network or the db connection or the parsing or .... is the bottleneck). If proxying does turn out to have an unacceptable impact, you can turn it off in the production system. If you plan to do that, you should explicitly test that application behaviour is the same with and without proxying.
Of course, answers are different for (for example) an embedded enviroment, but I wouldn't really want to use avalon in one of those.
cheers!
- LSD
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
