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:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/sqlntsv/htm/nsp_advancedtopics_2b5f.asp
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/sqlntsv/htm/nsp_objectmodel2_4sdx.asp
- 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
http://www.microsoft.com/info/cpyright.htm.
Please do not send e-mail directly to this alias. This alias is for
newsgroup purposes only.
--
"Mert Sakarya" <msakarya@(nospam)e-kolay.com> wrote in message
news:e3WTOS6B...@TK2MSFTNGP15.phx.gbl...
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\XXX\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\XXX\DeliveryProtocol\HttpDeliveryProtocol.dll</Provider
assembly name>
</EventParameters>
</Context>
<Description>
Value cannot be null.
</Description>
<Instance>XXX</Instance>
<ApplicationName>XXX</ApplicationName>
<Component>Distributor</Component>
<ComponentDetails>
DistributorName: XXXDist1
</ComponentDetails>
<Thread>16</Thread>
</NotificationServicesEvent>
Can you help???
"Colin Meek [MSFT]" <CM...@online.microsoft.com> wrote in message
news:%23zacoz7...@TK2MSFTNGP09.phx.gbl...
- 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
http://www.microsoft.com/info/cpyright.htm.
Please do not send e-mail directly to this alias. This alias is for
newsgroup purposes only.
--
"Mert Sakarya" <msakarya@(nospam)e-kolay.com> wrote in message
news:#QD2NB8B...@TK2MSFTNGP09.phx.gbl...
Once one gets the notion, it is easy to enhance the system...
"Colin Meek [MSFT]" <CM...@online.microsoft.com> wrote in message
news:eVSmhbI...@TK2MSFTNGP15.phx.gbl...
From http://www.developmentnow.com/g/110_2005_1_0_0_403482/HTTPDeliveryProtocol.htm
Posted via DevelopmentNow.com Groups
http://www.developmentnow.com/g/