Hello,



Are there any inherent performance differences between CDO and other 3rd

party components (such as ASPMail or ASPQMail)?



I have pretty much always used ASPMail, but now the ability to send a lot of

messages is going to be an intricate part of my site, where as in the past

it was just a nice feature.



I particularly like the ability of ServerObjects new product ASPQMail to

allow a message to be queued so that the rest of the page loads up much

quicker.



Does CDO allow message queuing?



Any feed back would be very helpful.



Thanks,

Scott

I have always done this with my own VB COM object and a database.  I let

my ASP pages insert records that contain the contents of the email

message into a SQL table(s).  Then I have a COM object that checks for

any new records and uses CDO to send the actual email via Exchange.



This is totally scalable by adding additional COM servers if need be and

it allows the ASP pages to be processed as fast as possible, improving

the users satisfaction.  I believe it is poor programming practice to

have an end-user waiting for such an expensive process as sending an

email message...



You can also do this with MSMQ services too.



Mike.



-----Original Message-----

From: Scott Watermasysk [mailto:swatermasysk@C...]

Sent: Friday, January 19, 2001 5:27 AM

To: ASP CDO

Subject: [asp_cdo] CDO vs. Others



Hello,



Are there any inherent performance differences between CDO and other 3rd

party components (such as ASPMail or ASPQMail)?



I have pretty much always used ASPMail, but now the ability to send a

lot of

messages is going to be an intricate part of my site, where as in the

past

it was just a nice feature.



I particularly like the ability of ServerObjects new product ASPQMail to

allow a message to be queued so that the rest of the page loads up much

quicker.



Does CDO allow message queuing?



Any feed back would be very helpful.



Thanks,

Scott