Posted by ezra-g on April 28, 2008 at 9:01pm
Jump to:
| Project: | Collect Nodes |
| Version: | 5.x-1.0-beta2 |
| Component: | Code |
| Category: | support request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | postponed (maintainer needs more info) |
Issue Summary
Could you clarify what the difference between this module and the nodequeue module?
Comments
#1
To my belief, nodequeue business is about letting administrators manage specific queues of nodes. So I will say that nodequeue focuses on the "how it's stored" and the "business logic/management" of nodes once they are listed. For now on, node_queue is not end-user oriented, and that usecase, to my knowledge, will be solved by the end of the GSoc.
This (collect_nodes) is much more about how it's going to enter in the storage. My guess is it will be possible to make that an entry point widget for an advanced node_queue "backend", at least I would look that way to make the connection with node_queue. (actually, I'm gona need that, so this is definitely an open strategic key point).
Would you be interested in this kind of evolution?
Collect_nodes can also be seen as one of the firsts module truly [services / json server / service json endpoint / widget client] developped. This powerful architecture, by the way, is not really going to happen if we keep using "hook_link" to display additional services on a node... The huge question behind that is, why can it be better at some point ? Well, this is WebService, and Google will explain better than me the usecase advantages to that (agility, low-coupled architectures, ...).
Anyway, I'll be more than happy to make it converge with node_queue in a smart way, or to give any webservice magic to the class of services one can call "node_pluggable_services". (usually hook_links()...), which includes nodequeue.
Hope I answered your question...
#2
It sounds like you're saying that your project could use nodequeue to store data and provide enhanced ways of accessing\interacting with that data. If that's correct, it sounds like your project could be merged into nodequeue or be written as a nodequeue companion module.
#3
I do agree with that on a mid-term strategy plan, but I thought I also pointed out some specific issues to that for the present day:
As for the understanding of what collect_nodes does, it totally does what you've said.
However, if anyone feels the need to make the convergence happen right now, I'll be more than happy to help. I'm just not sure doing that right now is the best bet in terms of release managment.
Regards,