Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Raising Events 1

Status
Not open for further replies.

Apinedo

Programmer
Oct 5, 2000
6
CO
Hi.
I am working with MTS and I have heard that Raising Events are a bad idea.
Is it true?
I have heard Raising Events may not work with some vertions of Windows98.

Thanks
 
Can you describe in detail such as using VB/Delphi,etc?

Regards! [sig][/sig]
 
Hi zallen.
Well, I am working with Visual Basic 6.0.
I need that my MTS component sends continuously information to the client but I don't want the component stops its execution (I dont want that the method finishes to return information).

I thougth it was a good idea (I am talking about using Raising Events) but I found an article ( and now
I don't know what to do.

Please read the article and then write me.

Thanks [sig][/sig]
 

Apinedo,

Every book and article that I read discourages the use of Events from MTS components. Actually, it is discouraged from any Data-Centric Business Object -- basically any back-end ActiveX DLL or ActiveX EXE. Two way communication complicates matters and has a bad effect on network traffic.

I understand if you don't want to send back a ton of parameters from your methods; however, you can try to send back one parameter that serializes all of data that you need to send back. Have you thought of using PropertyBag objects?

Tarek [sig][/sig]
 
Maybe you should use callback to send message to client from your components!

Moreover you can use MSMQ to send asynchronous message !

In a short word,i think using other technology may be a good choice instead of raising events!

Hope it helps!

Regards! [sig][/sig]
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top