-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Ken Rickard schrieb:
Well, just to be clear, my biggest issue with core aggregator has long been that it is not an API, so you cannot call most aggregator functions outside of the context of the core module. This is a problem when trying to extend its functionality, and why FeedAPI (and the push for FeedAPI in core) was created.
I can't understand why somebody remotely cares about such ephemeral things as feeds. :p
Killes, since I know you have used MySite, take a look at the kludge I had to write to allow users to add feeds there -- aggregator in
Frankly: Mysite was full of cludges at the time I used it (over a year ago).
core should support that feature (e.g. non-admins adding feeds to a collection), but did not (and probably still does not).
So I think that supports the statement that aggregator code is "below" the node module, for instance.
Should we add new features to aggregator? Maybe not. But it needs an architecture overhaul.
Ok, it you can make it more API-like while not bloating it too much, I can live with that.
One that is better done in contrib, as it turns out.
Still not sure I buy that. How should a core committer review the resulting patch? It will be a "take all or leave it" thing. And I think that the result might be "leave it". Cheers, Gerhard -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAknuMzAACgkQfg6TFvELooQyeACff1yIVZZW8wJM4HdjU3k/M+f2 5W8AoI3kC0Q/RbVcOG3Nz993lQb5wfpB =kFnL -----END PGP SIGNATURE-----