Re: Custom subscription .NET Feed URL
54 views
Skip to first unread message
Brian Dunnington
Jun 30, 2012, 3:05:21 PM6/30/12
to growl-fo...@googlegroups.com
I think there might be a misunderstanding of what each of the pieces is doing.
A custom feed subscription plugin would be used to consume some data source that was providing information that you wanted to be notified about. So the RSS/Atom Feed subscriber polls a feed and generates notifications when new items are found. If you had an RSS or Atom feed that you wanted to monitor, you wouldnt need to create a new custom plugin - you could just use the existing one and point it at your feed's url.
If you did have a need to create a custom subscription plugin, it would be because you had another source of data that you wanted to monitor. That data source (some custom webservice or a process running on your machine or whatever) would dictate how you implemented the subscription plugin (so that it could connect to the service, parse whatever information it provides, and generate the notifications).
If you implemented a custom forwarder already, where did you forward the data to and in what format? If you forwarded the data to a webservice of some kind, then your custom subscription plugin would need to connect to that same webservice and read the data. If you are trying to 'cut out the middle man' and create a forwarder that uses Growl itself that you can subscribe to, that will be trickier. Assuming you would be subscribing from another machine, you would have to create your forwarder in such a way that it exposed a server that could be connected to. That is beyond the scope of this response, but essentially you would have to log each message that the forwarder received, create some kind of listening socket, and when connections to that socket came in, you would have to spit out the logged messages in some kind of structured format. Then your subscription plugin would need to connect to that server and parse that structured data response.
Maybe if you describe what your original goal was, I could offer up some more specific ideas on how to achieve it.
A custom feed subscription plugin would be used to consume some data source that was providing information that you wanted to be notified about. So the RSS/Atom Feed subscriber polls a feed and generates notifications when new items are found. If you had an RSS or Atom feed that you wanted to monitor, you wouldnt need to create a new custom plugin - you could just use the existing one and point it at your feed's url.
If you did have a need to create a custom subscription plugin, it would be because you had another source of data that you wanted to monitor. That data source (some custom webservice or a process running on your machine or whatever) would dictate how you implemented the subscription plugin (so that it could connect to the service, parse whatever information it provides, and generate the notifications).
If you implemented a custom forwarder already, where did you forward the data to and in what format? If you forwarded the data to a webservice of some kind, then your custom subscription plugin would need to connect to that same webservice and read the data. If you are trying to 'cut out the middle man' and create a forwarder that uses Growl itself that you can subscribe to, that will be trickier. Assuming you would be subscribing from another machine, you would have to create your forwarder in such a way that it exposed a server that could be connected to. That is beyond the scope of this response, but essentially you would have to log each message that the forwarder received, create some kind of listening socket, and when connections to that socket came in, you would have to spit out the logged messages in some kind of structured format. Then your subscription plugin would need to connect to that server and parse that structured data response.
Maybe if you describe what your original goal was, I could offer up some more specific ideas on how to achieve it.
On Thu, Jun 28, 2012 at 4:14 AM, Jean-Paul Thorne <thorne.j...@gmail.com> wrote:
I'm trying to implement a custom feed subscription plugin, similar to the RSS/Atom Feed Subscriber. Been searching the forums but can't seem to find any useful info.
I have downloaded the Growl Subscriber SDK, and implemented a solution in .NET, VS 2010. I get the plugin to "install"/growl to pickup the plugin, but am quite stumped as to what to enter as the "feed url".So I suppose my question is "How do I create my own feed to which a client could subscribe"?For example, having implemented a custom forwarder application, using the Custom Forwarder SDK, I attempt to enter something like: http://localhost:2751/Home as the URL but get an error "Could not parse feed".Any help much appreciated!--
You received this message because you are subscribed to the Google Groups "growl for windows" group.
To view this discussion on the web visit https://groups.google.com/d/msg/growl-for-windows/-/pBMJ0zBJxFsJ.
To post to this group, send email to growl-fo...@googlegroups.com.
To unsubscribe from this group, send email to growl-for-wind...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/growl-for-windows?hl=en.
Reply all
Reply to author
Forward
0 new messages