exposing Simplenews module API

Awesome, and perfect timing. I need this right now.

But, I'm not sure whether this should go in Services core. I think services core should really only contain services for core modules (I make an exception for views), and contrib modules would have additional modules for services. I realize this is a bit of work to open up a whole new project for such a module as this, but ideally, it should become part of the simplenews module, IMO.

I'm open to discussion on this...

When coding services, I imagined that someday it might replace core xmlrpc. Then, with services part of core, each core module and contrib module would be in charge of providing service hooks, through separate "_service" modules.

Thanks for your work on this.

Scott

I totally agree about it being overkill. Personally I'd like to see existing modules start to include service hooks, in the same way that they might hook into other contrib modules like views or cck. I don't really know if the community cares enough about services yet to do that though. As for a single contrib module with a bunch of random services, don't know about that either, seems like it would be bloat.

I think the best solution for now would be either to get simplenews to include the module in their project, or to just create a new project that you will probably never have to touch after setup.

Scott

This should be added to the Simplenews module as opposed to being added to the Services module. Could actually be part of simplenews.module instead of its own thing.

This can be a candidate for Simplenews for Drupal-6. I will look into it.

Flagged as reminder for simplenews-6.x developement

This probably needs to be ported.

Apparently, there already is an issue with a patch for D6 : #221521: SimpleNews Service.

Setting this to duplicate although it was before..

Please update the referenced patch to 6.x-2.x and add unsubscribe support.
But most importantly - what i also miss here - is a permission check.