Is this module 4.7 ready

Yes, they work in 4.7.

Testing is currently underway. You are welcome to join in. Install the publish module as you'd expect. Click on administer - publish and explore. Install the subscribe module on another site. Click on administer - subscribe and point it to your publishing site.

I will work on the README soon. In the meantime, I'll copy/paste the following:

Currently publish/subscribe publishes certain node types and optionally their associated vocabulary terms from a publishing site to a subscribing site.

To establish a subscription, the subscribing site must provide credentials that the publishing site agrees are good enough. This is set per-channel on the publishing site. Current authentication methods are:

- no authentication
- using a Drupal permission called 'subscribe to channels'
- with a username and password assigned to a channel

Plus there's domain-restricted security.

Once a subscription is established, the subscribing site may "pull" nodes from the publishing site (or have new nodes "pushed" to it). The subscribing site may give conditions describing what nodes it wants. E.g.,

nid = 1234

or

changed > (some unix time)
Section = blueberry

So, to get around to your question, the entire framework is already there.

It should be noted that the conversation goes like this:

Subscriber: may I subscribe to channel 4? Here's username foo, password bar

Publisher: yes, you may; here's a description of the channel. It's called "Butter" and the description is "Publishing butter-related information since 2005." We publish nodetype story and associated vocabularies Color and Flavor, and we publish nodetype page and associated vocabulary Color.

So there's the ability of someone with the proper credentials to get information about a channel, which is really a set of data (since channels themselves have conditions, like Flavor = Buttery.

When you set up a channel, there's also the ability to check the Advertise checkbox, which adds the channel to the list of info a site receives when it tries to find out what public channels are available on the site by calling drupal.publish.getChannels. So that's just name and description, not any more information -- you need credentials to get more information and subscribe. I'm imagining that in the future AJAX would get this as part of the subscription process -- "I want to subscribe to drupal.org; what channels are available?"

Thanks. I'll let you know how it goes. It might make sense to integrate this with views modules in some way so that publishing and subscribing could happen within the views interface???