HTTPDeliveryProtocol

Thanks. I have done that...

HTTPDeliveryProtocol is like.... (which compiled fine)

using System;
using Microsoft.SqlServer.NotificationServices;
using System.Net;

namespace HTTPDeliveryProtocol {
public class HTTPDeliveryProtocol : IHttpProtocolProvider
.......


And My Configuration file contains...

<Protocols>
<Protocol>
<ProtocolName>SMS</ProtocolName>
<ClassName>HttpExtension</ClassName>
</Protocol>
</Protocols>

<DeliveryChannels>
<DeliveryChannel>
<DeliveryChannelName>SMSChannel</DeliveryChannelName>
<ProtocolName>SMS</ProtocolName>
<Arguments>
<Argument>
<Name>ProtocolProviderClassName</Name>
<Value>HTTPDeliveryProtocol</Value>
</Argument>
<Argument>
<Name>ProtocolProviderAssemblyName</Name>
<Value>C:\SQL-NS\XX\DeliveryProtocol\HttpDeliveryProtocol.dll</Value>
</Argument>
<Argument>
<Name>PostURL</Name>
<Value>http://localhost/webapplication2/data.aspx</Value>
</Argument>
</Arguments>
</DeliveryChannel>

ADF contains...
<Protocols>
<Protocol>
<ProtocolName>SMS</ProtocolName>
<Fields>
<Field><FieldName>BodyFormat</FieldName><SqlExpression>N'text'</SqlExpression></Field>
</Fields>
</Protocol>
Note I don't use the BodyFormat field. But I will...

I subscribed a user to the SMS Channel... When I fire an event, File evens
work fine, but SMS events give the following error in my Event Log

<NotificationServicesEvent>
<Description>
The protocol provider could not be loaded because the assembly or class
name is not valid.
</Description>
<Context>
<EventParameters>
<Protocol name>SMS</Protocol name>
<Provider class name>HTTPDeliveryProtocol</Provider class name>
<Provider assembly
name>C:\SQL-NS\XX\DeliveryProtocol\HttpDeliveryProtocol.dll</Provider
assembly name>
</EventParameters>

</Context>
<Description>
Value cannot be null.
</Description>
<Instance>XX</Instance>
<ApplicationName>XX</ApplicationName>
<Component>Distributor</Component>
<ComponentDetails>
DistributorName: XXDist1
</ComponentDetails>
<Thread>16</Thread>
</NotificationServicesEvent>

Can you help???




"Colin Meek [MSFT]" wrote in message

 > Hi Mert,
 >
 > I would suggest implementing the IHttpProtocolProvider interface, which
 > allow NS to handle most of the infrastructure you require, including
 > asynchronous requests.
 >
 > You can find more information in NS books online:
 >
<font color=purple> > <a rel="nofollow" style='text-decoration: none;' href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/sqlntsv/htm/nsp_advancedtopics_2b5f.asp</font" target="_blank">http://msdn.microsoft.com/library/default.asp?url=/library/en-us/sqlnt...htm/nsp</a>>
<font color=purple> > <a rel="nofollow" style='text-decoration: none;' href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/sqlntsv/htm/nsp_objectmodel2_4sdx.asp</font" target="_blank">http://msdn.microsoft.com/library/default.asp?url=/library/en-us/sqlnt...htm/nsp</a>>
 >
 > - Colin Meek [MSFT]
 >
 > --
 > This posting is provided "AS IS" with no warranties, and confers no
 > rights.
 > Use of included script samples are subject to the terms specified at
<font color=purple> > <a rel="nofollow" style='text-decoration: none;' href="http://www.microsoft.com/info/cpyright.htm.</font" target="_blank">http://www.microsoft.com/info/cpyright.htm.</font</a>>
 >
 > Please do not send e-mail directly to this alias. This alias is for
 > newsgroup purposes only.
 > --
 >


  >> Is it logical to implement an "HTTPDeliveryProtocol" which makes
  >> thousands
  >> of request to a web server - may be some server in the same network,
  >> which
  >> can handle 200 requests per second ?
  >> Or should I implement a "MQDeliveryProtocol" which makes HTTPRequests,
  >> asynchronously (where I cannot keep track of a notifications whether
  >> they
  >> are succeeded)?
  >>
  >> Mert
  >>
  >>
 >
 >
 >> Stay informed about: HTTPDeliveryProtocol 

You need to include the namespace for "ProtocolProviderClassName" as well.

- Colin Meek [MSFT]

--
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
<a rel="nofollow" style='text-decoration: none;' href="http://www.microsoft.com/info/cpyright.htm." target="_blank">http://www.microsoft.com/info/cpyright.htm.</a>

Please do not send e-mail directly to this alias. This alias is for
newsgroup purposes only.
--

"Mert Sakarya" wrote in message
news:#QD2NB8BFHA.1564@TK2MSFTNGP09.phx.gbl...
 > Thanks. I have done that...
 >
 > HTTPDeliveryProtocol is like.... (which compiled fine)
 >
 > using System;
 > using Microsoft.SqlServer.NotificationServices;
 > using System.Net;
 >
 > namespace HTTPDeliveryProtocol {
 > public class HTTPDeliveryProtocol : IHttpProtocolProvider
 > .......
 >
 >
 > And My Configuration file contains...
 >
 > <Protocols>
 > <Protocol>
 > <ProtocolName>SMS</ProtocolName>
 > <ClassName>HttpExtension</ClassName>
 > </Protocol>
 > </Protocols>
 >
 > <DeliveryChannels>
 > <DeliveryChannel>
 > <DeliveryChannelName>SMSChannel</DeliveryChannelName>
 > <ProtocolName>SMS</ProtocolName>
 > <Arguments>
 > <Argument>
 > <Name>ProtocolProviderClassName</Name>
 > <Value>HTTPDeliveryProtocol</Value>
 > </Argument>
 > <Argument>
 > <Name>ProtocolProviderAssemblyName</Name>
 >
<Value>C:\SQL-NS\XX\DeliveryProtocol\HttpDeliveryProtocol.dll</Value>
 > </Argument>
 > <Argument>
 > <Name>PostURL</Name>
 > <Value>http://localhost/webapplication2/data.aspx</Value>
 > </Argument>
 > </Arguments>
 > </DeliveryChannel>
 >
 > ADF contains...
 > <Protocols>
 > <Protocol>
 > <ProtocolName>SMS</ProtocolName>
 > <Fields>
 >
<Field><FieldName>BodyFormat</FieldName><SqlExpression>N'text'</Sq
lExpression></Field>
 > </Fields>
 > </Protocol>
 > Note I don't use the BodyFormat field. But I will...
 >
 > I subscribed a user to the SMS Channel... When I fire an event, File evens
 > work fine, but SMS events give the following error in my Event Log
 >
 > <NotificationServicesEvent>
 > <Description>
 > The protocol provider could not be loaded because the assembly or class
 > name is not valid.
 > </Description>
 > <Context>
 > <EventParameters>
 > <Protocol name>SMS</Protocol name>
 > <Provider class name>HTTPDeliveryProtocol</Provider class name>
 > <Provider assembly
 > name>C:\SQL-NS\XX\DeliveryProtocol\HttpDeliveryProtocol.dll</Provider
 > assembly name>
 > </EventParameters>
 >
 > </Context>
 > <Description>
 > Value cannot be null.
 > </Description>
 > <Instance>XX</Instance>
 > <ApplicationName>XX</ApplicationName>
 > <Component>Distributor</Component>
 > <ComponentDetails>
 > DistributorName: XXDist1
 > </ComponentDetails>
 > <Thread>16</Thread>
 > </NotificationServicesEvent>
 >
 > Can you help???
 >
 >
 >
 >


  > > Hi Mert,
  > >
  > > I would suggest implementing the IHttpProtocolProvider interface, which
  > > allow NS to handle most of the infrastructure you require, including
  > > asynchronous requests.
  > >
  > > You can find more information in NS books online:
  > >
  > >
<a rel="nofollow" style='text-decoration: none;' href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/sqlntsv/htm/nsp_advancedtopics_2b5f.asp" target="_blank">http://msdn.microsoft.com/library/default.asp?url=/library/en-us/sqlnt...htm/nsp</a>
  > >
<a rel="nofollow" style='text-decoration: none;' href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/sqlntsv/htm/nsp_objectmodel2_4sdx.asp" target="_blank">http://msdn.microsoft.com/library/default.asp?url=/library/en-us/sqlnt...htm/nsp</a>
  > >
  > > - Colin Meek [MSFT]
  > >
  > > --
  > > This posting is provided "AS IS" with no warranties, and confers no
  > > rights.
  > > Use of included script samples are subject to the terms specified at
<font color=green>  > > <a rel="nofollow" style='text-decoration: none;' href="http://www.microsoft.com/info/cpyright.htm.</font" target="_blank">http://www.microsoft.com/info/cpyright.htm.</font</a>>
  > >
  > > Please do not send e-mail directly to this alias. This alias is for
  > > newsgroup purposes only.
  > > --
  > >


   > >> Is it logical to implement an "HTTPDeliveryProtocol" which makes
   > >> thousands
   > >> of request to a web server - may be some server in the same network,
   > >> which
   > >> can handle 200 requests per second ?
   > >> Or should I implement a "MQDeliveryProtocol" which makes HTTPRequests,
   > >> asynchronously (where I cannot keep track of a notifications whether
   > >> they
   > >> are succeeded)?
   > >>
   > >> Mert
   > >>
   > >>
  > >
  > >
 >
 >
 >> Stay informed about: HTTPDeliveryProtocol 

Thanks. Worked. This thing is cool!!!

Once one gets the notion, it is easy to enhance the system...


"Colin Meek [MSFT]" wrote in message

 > You need to include the namespace for "ProtocolProviderClassName" as well.
 >
 > - Colin Meek [MSFT]
 >
 > --
 > This posting is provided "AS IS" with no warranties, and confers no
 > rights.
 > Use of included script samples are subject to the terms specified at
<font color=purple> > <a rel="nofollow" style='text-decoration: none;' href="http://www.microsoft.com/info/cpyright.htm.</font" target="_blank">http://www.microsoft.com/info/cpyright.htm.</font</a>>
 >
 > Please do not send e-mail directly to this alias. This alias is for
 > newsgroup purposes only.
 > --
 >


  >> Thanks. I have done that...
  >>
  >> HTTPDeliveryProtocol is like.... (which compiled fine)
  >>
  >> using System;
  >> using Microsoft.SqlServer.NotificationServices;
  >> using System.Net;
  >>
  >> namespace HTTPDeliveryProtocol {
  >> public class HTTPDeliveryProtocol : IHttpProtocolProvider
  >> .......
  >>
  >>
  >> And My Configuration file contains...
  >>
  >> <Protocols>
  >> <Protocol>
  >> <ProtocolName>SMS</ProtocolName>
  >> <ClassName>HttpExtension</ClassName>
  >> </Protocol>
  >> </Protocols>
  >>
  >> <DeliveryChannels>
  >> <DeliveryChannel>
  >> <DeliveryChannelName>SMSChannel</DeliveryChannelName>
  >> <ProtocolName>SMS</ProtocolName>
  >> <Arguments>
  >> <Argument>
  >> <Name>ProtocolProviderClassName</Name>
  >> <Value>HTTPDeliveryProtocol</Value>
  >> </Argument>
  >> <Argument>
  >> <Name>ProtocolProviderAssemblyName</Name>
  >>
 > <Value>C:\SQL-NS\XX\DeliveryProtocol\HttpDeliveryProtocol.dll</Value>
  >> </Argument>
  >> <Argument>
  >> <Name>PostURL</Name>
  >> <Value>http://localhost/webapplication2/data.aspx</Value>
  >> </Argument>
  >> </Arguments>
  >> </DeliveryChannel>
  >>
  >> ADF contains...
  >> <Protocols>
  >> <Protocol>
  >> <ProtocolName>SMS</ProtocolName>
  >> <Fields>
  >>
 > <Field><FieldName>BodyFormat</FieldName><SqlExpression>N'text'</Sq
 > lExpression></Field>
  >> </Fields>
  >> </Protocol>
  >> Note I don't use the BodyFormat field. But I will...
  >>
  >> I subscribed a user to the SMS Channel... When I fire an event, File
  >> evens
  >> work fine, but SMS events give the following error in my Event Log
  >>
  >> <NotificationServicesEvent>
  >> <Description>
  >> The protocol provider could not be loaded because the assembly or class
  >> name is not valid.
  >> </Description>
  >> <Context>
  >> <EventParameters>
  >> <Protocol name>SMS</Protocol name>
  >> <Provider class name>HTTPDeliveryProtocol</Provider class name>
  >> <Provider assembly
  >> name>C:\SQL-NS\XX\DeliveryProtocol\HttpDeliveryProtocol.dll</Provider
  >> assembly name>
  >> </EventParameters>
  >>
  >> </Context>
  >> <Description>
  >> Value cannot be null.
  >> </Description>
  >> <Instance>XX</Instance>
  >> <ApplicationName>XX</ApplicationName>
  >> <Component>Distributor</Component>
  >> <ComponentDetails>
  >> DistributorName: XXDist1
  >> </ComponentDetails>
  >> <Thread>16</Thread>
  >> </NotificationServicesEvent>
  >>
  >> Can you help???
  >>
  >>
  >>
  >>


   >> > Hi Mert,
   >> >
   >> > I would suggest implementing the IHttpProtocolProvider interface, which
   >> > allow NS to handle most of the infrastructure you require, including
   >> > asynchronous requests.
   >> >
   >> > You can find more information in NS books online:
   >> >
   >> >
<font color=purple> > <a rel="nofollow" style='text-decoration: none;' href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/sqlntsv/htm/nsp_advancedtopics_2b5f.asp</font" target="_blank">http://msdn.microsoft.com/library/default.asp?url=/library/en-us/sqlnt...htm/nsp</a>>
   >> >
<font color=purple> > <a rel="nofollow" style='text-decoration: none;' href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/sqlntsv/htm/nsp_objectmodel2_4sdx.asp</font" target="_blank">http://msdn.microsoft.com/library/default.asp?url=/library/en-us/sqlnt...htm/nsp</a>>
   >> >
   >> > - Colin Meek [MSFT]
   >> >
   >> > --
   >> > This posting is provided "AS IS" with no warranties, and confers no
   >> > rights.
   >> > Use of included script samples are subject to the terms specified at
<font color=brown>   >> > <a rel="nofollow" style='text-decoration: none;' href="http://www.microsoft.com/info/cpyright.htm.</font" target="_blank">http://www.microsoft.com/info/cpyright.htm.</font</a>>
   >> >
   >> > Please do not send e-mail directly to this alias. This alias is for
   >> > newsgroup purposes only.
   >> > --
   >> >


   >> >> Is it logical to implement an "HTTPDeliveryProtocol" which makes
   >> >> thousands
   >> >> of request to a web server - may be some server in the same network,
   >> >> which
   >> >> can handle 200 requests per second ?
   >> >> Or should I implement a "MQDeliveryProtocol" which makes HTTPRequests,
   >> >> asynchronously (where I cannot keep track of a notifications whether
   >> >> they
   >> >> are succeeded)?
   >> >>
   >> >> Mert
   >> >>
   >> >>
   >> >
   >> >
  >>
  >>
 >
 >
 >> Stay informed about: HTTPDeliveryProtocol 

hi Mert,
I am developing the same kind of application that notifies using sms.
can you help me out with some sample code for the custom delivery protocol?

From http://www.developmentnow.com/g/110_2005_1_0_0_403482/HTTPDeliveryProtocol.htm

Posted via DevelopmentNow.com Groups
http://www.developmentnow.com/g/
 >> Stay informed about: HTTPDeliveryProtocol