dcsimg
Login | Register   
LinkedIn
Google+
Twitter
RSS Feed
Download our iPhone app
TODAY'S HEADLINES  |   ARTICLE ARCHIVE  |   FORUMS  |   TIP BANK
Browse DevX
Sign up for e-mail newsletters from DevX

By submitting your information, you agree that devx.com may send you DevX offers via email, phone and text message, as well as email offers about other products and services that DevX believes may be of interest to you. DevX will process your information in accordance with the Quinstreet Privacy Policy.


Tip of the Day
Language: Enterprise
Expertise: Advanced
Oct 26, 1999

WEBINAR:

On-Demand

Building the Right Environment to Support AI, Machine Learning and Deep Learning


MTS and Passing Direct Reference

MTS objects clients should never have access to unsafe references. A client application should never be passed a direct reference to an MTS object. Once such a reference is passed outside the object's context, it is no longer a valid reference. SafeRef function should be used by an object to obtain a reference to itself that's safe to pass outside its context (say to a client). This function returns a reference to the context wrapper instead of a reference to the object itself. If this is not done, then the client application can make a call on the MTS object without going through the context wrapper. This defeats the interception scheme set up by the MTS run time. For example:
 
Set MyObject = SafeRef (Me) and pass 
MyObject to the client application
Jai Bardhan
 
Comment and Contribute

 

 

 

 

 


(Maximum characters: 1200). You have 1200 characters left.

 

 

Sitemap
Thanks for your registration, follow us on our social networks to keep up-to-date