Visual Basic/VB, MTS DLL

MTS DLL

Author	Message
Kip Fryma #1 / 12	MTS DLL I want an MTS componant to raise an event that will affect all clients using the componant. With a standard AX DLL this would not be possible. But because the componant is running on MTS (Out of process) shouldn't a RaiseEvent raise an event for all clients who have an object referenced to this class in the MTS componant? Kip
Sat, 24 Jan 2004 21:37:10 GMT

Chris Heywoo #2 / 12	MTS DLL Would it not just Raise the Event for the specific thread? If this wasn't the case and you had some error handling code which raised an error when a transaction failed wouldn't all users of the object recieve the same error? Correct me if I'm wrong. Quote: > I want an MTS componant to raise an event that will affect all clients using > the componant. With a standard AX DLL this would not be possible. But > because the componant is running on MTS (Out of process) shouldn't a > RaiseEvent raise an event for all clients who have an object referenced to > this class in the MTS componant? > Kip
Sat, 24 Jan 2004 21:35:36 GMT

Kip Fryma #3 / 12	MTS DLL Yes i suppose the event would be raised in its own thread so it would have to be a single threaded componant.... Hopefully someone else can clue in about the error handling bit... Quote: > Would it not just Raise the Event for the specific thread? If this wasn't > the case and you had some error handling code which raised an error when a > transaction failed wouldn't all users of the object recieve the same error? > Correct me if I'm wrong. > Chris.Heywood > > I want an MTS componant to raise an event that will affect all clients > using > > the componant. With a standard AX DLL this would not be possible. But > > because the componant is running on MTS (Out of process) shouldn't a > > RaiseEvent raise an event for all clients who have an object referenced to > > this class in the MTS componant? > > Kip
Sat, 24 Jan 2004 21:53:28 GMT

Chris Heywoo #4 / 12	MTS DLL What exactly (or more precisely) is it you are trying to achieve? Quote: > Yes i suppose the event would be raised in its own thread so it would have > to be a single threaded componant.... > Hopefully someone else can clue in about the error handling bit... > > Would it not just Raise the Event for the specific thread? If this wasn't > > the case and you had some error handling code which raised an error when a > > transaction failed wouldn't all users of the object recieve the same > error? > > Correct me if I'm wrong. > > Chris.Heywood > > > I want an MTS componant to raise an event that will affect all clients > > using > > > the componant. With a standard AX DLL this would not be possible. But > > > because the componant is running on MTS (Out of process) shouldn't a > > > RaiseEvent raise an event for all clients who have an object referenced > to > > > this class in the MTS componant? > > > Kip
Sat, 24 Jan 2004 21:54:49 GMT

Kip Fryma #5 / 12	MTS DLL I have my componant with many classes running on MTS... I want to raise an event that notifies each client that this event has happened. Quote: > What exactly (or more precisely) is it you are trying to achieve? > Chris.Heywood > > Yes i suppose the event would be raised in its own thread so it would have > > to be a single threaded componant.... > > Hopefully someone else can clue in about the error handling bit... > > > Would it not just Raise the Event for the specific thread? If this > wasn't > > > the case and you had some error handling code which raised an error when > a > > > transaction failed wouldn't all users of the object recieve the same > > error? > > > Correct me if I'm wrong. > > > Chris.Heywood > > > > I want an MTS componant to raise an event that will affect all clients > > > using > > > > the componant. With a standard AX DLL this would not be possible. > But > > > > because the componant is running on MTS (Out of process) shouldn't a > > > > RaiseEvent raise an event for all clients who have an object > referenced > > to > > > > this class in the MTS componant? > > > > Kip
Sat, 24 Jan 2004 23:06:12 GMT

Chris Heywoo #6 / 12	MTS DLL Don't really know then, I only use MTS thru IIS and would therefore have no real need for this type of functionality. Quote: > I have my componant with many classes running on MTS... > I want to raise an event that notifies each client that this event has > happened. > > What exactly (or more precisely) is it you are trying to achieve? > > Chris.Heywood > > > Yes i suppose the event would be raised in its own thread so it would > have > > > to be a single threaded componant.... > > > Hopefully someone else can clue in about the error handling bit... message > > > > Would it not just Raise the Event for the specific thread? If this > > wasn't > > > > the case and you had some error handling code which raised an error > when > > a > > > > transaction failed wouldn't all users of the object recieve the same > > > error? > > > > Correct me if I'm wrong. > > > > Chris.Heywood > > > > > I want an MTS componant to raise an event that will affect all > clients > > > > using > > > > > the componant. With a standard AX DLL this would not be possible. > > But > > > > > because the componant is running on MTS (Out of process) shouldn't a > > > > > RaiseEvent raise an event for all clients who have an object > > referenced > > > to > > > > > this class in the MTS componant? > > > > > Kip
Sat, 24 Jan 2004 23:17:16 GMT

Darryl Sever #7 / 12	MTS DLL Why don't you try a different approach. I pondered over a similar situation outside of MTS, and came up with a subscription model. Record all interested parties in a database and contact them when required. There is a difficulty in contacting a specific instance of a COM object this way, as you need to have access to the Running Object Table which is not an easy thing in VB. However I only needed any available instance, and that worked. Darryl Quote: > Don't really know then, I only use MTS thru IIS and would therefore have no > real need for this type of functionality. > Chris.Heywood > > I have my componant with many classes running on MTS... > > I want to raise an event that notifies each client that this event has > > happened. > > > What exactly (or more precisely) is it you are trying to achieve? > > > Chris.Heywood > > > > Yes i suppose the event would be raised in its own thread so it would > > have > > > > to be a single threaded componant.... > > > > Hopefully someone else can clue in about the error handling bit... > message > > > > > Would it not just Raise the Event for the specific thread? If this > > > wasn't > > > > > the case and you had some error handling code which raised an error > > when > > > a > > > > > transaction failed wouldn't all users of the object recieve the same > > > > error? > > > > > Correct me if I'm wrong. > > > > > Chris.Heywood > > > > > > I want an MTS componant to raise an event that will affect all > > clients > > > > > using > > > > > > the componant. With a standard AX DLL this would not be possible. > > > But > > > > > > because the componant is running on MTS (Out of process) shouldn't > a > > > > > > RaiseEvent raise an event for all clients who have an object > > > referenced > > > > to > > > > > > this class in the MTS componant? > > > > > > Kip
Sun, 25 Jan 2004 10:46:23 GMT

Kip Fryma #8 / 12	MTS DLL I am intrigued.. Could you give me a little more detail... Quote: > Why don't you try a different approach. I pondered over a similar situation > outside of MTS, and came up with a subscription model. Record all interested > parties in a database and contact them when required. There is a difficulty > in contacting a specific instance of a COM object this way, as you need to > have access to the Running Object Table which is not an easy thing in VB. > However I only needed any available instance, and that worked. > Darryl > > Don't really know then, I only use MTS thru IIS and would therefore have > no > > real need for this type of functionality. > > Chris.Heywood > > > I have my componant with many classes running on MTS... > > > I want to raise an event that notifies each client that this event has > > > happened. message > > > > What exactly (or more precisely) is it you are trying to achieve? > > > > Chris.Heywood > > > > > Yes i suppose the event would be raised in its own thread so it > would > > > have > > > > > to be a single threaded componant.... > > > > > Hopefully someone else can clue in about the error handling bit... > > message > > > > > > Would it not just Raise the Event for the specific thread? If > this > > > > wasn't > > > > > > the case and you had some error handling code which raised an > error > > > when > > > > a > > > > > > transaction failed wouldn't all users of the object recieve the > same > > > > > error? > > > > > > Correct me if I'm wrong. > > > > > > Chris.Heywood > > > > > > > I want an MTS componant to raise an event that will affect all > > > clients > > > > > > using > > > > > > > the componant. With a standard AX DLL this would not be > possible. > > > > But > > > > > > > because the componant is running on MTS (Out of process) > shouldn't > > a > > > > > > > RaiseEvent raise an event for all clients who have an object > > > > referenced > > > > > to > > > > > > > this class in the MTS componant? > > > > > > > Kip
Sun, 25 Jan 2004 21:13:11 GMT

Hercules Gunte #9 / 12	MTS DLL Am I understanding this correctly? You have a component servicing multiple requests from multiple clients. One client encounters something unexpected, and you then want to break every other client? Quote: > I want an MTS componant to raise an event that will affect all clients using > the componant. With a standard AX DLL this would not be possible. But > because the componant is running on MTS (Out of process) shouldn't a > RaiseEvent raise an event for all clients who have an object referenced to > this class in the MTS componant? > Kip
Mon, 26 Jan 2004 22:33:12 GMT

Kip Fryma #10 / 12	MTS DLL No that is not correct. I don't want to notify errors. Basically just messages from the server to notify all clients. A message could be anything but not a run time error on the server. Say for an example the server application was not able to automate a common ftp process. This information has to be relayed to the end users. Well what better way than to send a message to the client applications saying that an error has occured trying to connect to ftp.blahblahblah.com. You will have to restart this process manually. Or give some problems and solutions.... I woud like this to pop up on all clients using the client software notifying them of these occurances so they can respond to them in a timely fashion. Kip Quote: > Am I understanding this correctly? You have a component servicing multiple > requests from multiple clients. One client encounters something unexpected, and > you then want to break every other client? > > I want an MTS componant to raise an event that will affect all clients using > > the componant. With a standard AX DLL this would not be possible. But > > because the componant is running on MTS (Out of process) shouldn't a > > RaiseEvent raise an event for all clients who have an object referenced to > > this class in the MTS componant? > > Kip
Mon, 26 Jan 2004 23:45:05 GMT

Hercules Gunte #11 / 12	MTS DLL I would still say that you are likely to be advising a large number of people who don't care of something that probably won't be a problem for them. Even if you feel they would care, I would suggesting rather using an email notification, preferably to people such as administrators who can do something to cure the problem. This would allow you to send an email to a distribution list (single recipient, from the point of view of the app and leaves the details to the mail server), and anybody who has an interest could then be on the distribution list. Quote: > No that is not correct. I don't want to notify errors. Basically just > messages from the server to notify all clients. A message could be anything > but not a run time error on the server. Say for an example the server > application was not able to automate a common ftp process. This information > has to be relayed to the end users. Well what better way than to send a > message to the client applications saying that an error has occured trying > to connect to ftp.blahblahblah.com. You will have to restart this process > manually. Or give some problems and solutions.... > I woud like this to pop up on all clients using the client software > notifying them of these occurances so they can respond to them in a timely > fashion. > Kip > > Am I understanding this correctly? You have a component servicing > multiple > > requests from multiple clients. One client encounters something > unexpected, and > > you then want to break every other client? > > > I want an MTS componant to raise an event that will affect all clients > using > > > the componant. With a standard AX DLL this would not be possible. But > > > because the componant is running on MTS (Out of process) shouldn't a > > > RaiseEvent raise an event for all clients who have an object referenced > to > > > this class in the MTS componant? > > > Kip
Tue, 27 Jan 2004 23:00:17 GMT

Kip Fryma #12 / 12	MTS DLL I thought of that ..... I did some brainstorming and decided to take the approach I am taking. I began writing the code for a customizable email notification system but I scrapped it in favor of this system. I hope evrything is going to go well.. From the feedback I get from these newsgroups, notifications from a server machine to a client machine are rarely used and difficult to astain stability...... I guess they are rarely if ever implemented... Quote: > I would still say that you are likely to be advising a large number of people > who don't care of something that probably won't be a problem for them. Even if > you feel they would care, I would suggesting rather using an email notification, > preferably to people such as administrators who can do something to cure the > problem. This would allow you to send an email to a distribution list (single > recipient, from the point of view of the app and leaves the details to the mail > server), and anybody who has an interest could then be on the distribution list. > > No that is not correct. I don't want to notify errors. Basically just > > messages from the server to notify all clients. A message could be anything > > but not a run time error on the server. Say for an example the server > > application was not able to automate a common ftp process. This information > > has to be relayed to the end users. Well what better way than to send a > > message to the client applications saying that an error has occured trying > > to connect to ftp.blahblahblah.com. You will have to restart this process > > manually. Or give some problems and solutions.... > > I woud like this to pop up on all clients using the client software > > notifying them of these occurances so they can respond to them in a timely > > fashion. > > Kip > > > Am I understanding this correctly? You have a component servicing > > multiple > > > requests from multiple clients. One client encounters something > > unexpected, and > > > you then want to break every other client? > > > > I want an MTS componant to raise an event that will affect all clients > > using > > > > the componant. With a standard AX DLL this would not be possible. But > > > > because the componant is running on MTS (Out of process) shouldn't a > > > > RaiseEvent raise an event for all clients who have an object referenced > > to > > > > this class in the MTS componant? > > > > Kip
Wed, 28 Jan 2004 01:42:53 GMT

Page 1 of 1

[ 12 post ]