<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
<blockquote type="cite">Moreover, if event module is pointing to CCK,
then who owns the node<br>
type? CCK or event?</blockquote>
In content module you have all the content_insert, content_load,
content_*, so it looks like content.module owns those types and defines
those node hooks (and funky load callbacks). <span
class="moz-smiley-s1"><span> :-) </span></span><br>
<pre class="moz-signature" cols="72">Rob Roy Barreca
Founder and COO
Electronic Insight Corporation
<a class="moz-txt-link-freetext" href="http://www.electronicinsight.com">http://www.electronicinsight.com</a>
<a class="moz-txt-link-abbreviated" href="mailto:rob@electronicinsight.com">rob@electronicinsight.com</a></pre>
<br>
<br>
Khalid B wrote:
<blockquote
cite="mid4a9fdc630701031719v3a2430b7kf4cb934830a7bd73@mail.gmail.com"
type="cite">Suggestion 4 is interesting, and seems to be a viable
solution too.<br>
<br>
<div>
<blockquote class="gmail_quote"
style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">The
biggest disadvantage of this (which is quite obvious from looking
<br>
at the above example) is that it will be difficult to say when a<br>
module should or shouldn't assume ownership of node types, and that it<br>
will be easy for multiple modules to all assume ownership of node<br>
types, which would basically render the ordering of the hooks
<br>
redundant (since none of them choose to use 'alter').</blockquote>
<div><br>
Agreed. <br>
<br>
Moreover, if event module is pointing to CCK, then who owns the node<br>
type? CCK or event?<br>
</div>
</div>
<br>
Suggestion 5 builds on what Karoly said, which I am summarizing below.
<br>
<br>
- move all hook_load() and friends into hook_othernodeapi($op), where
$op is load, insert,<br>
delete, ...etc.<br>
- So, we have one real hook (hook_nodeapi($op)), and one callback
(hook_othernodeapi($op)).
<br>
<br>
(of course, othernodeapi has to be something better)<br>
<br>
This has the advantage of having only a maximum of two functions per
module, with ops of course.<br>
One for node creation modules, and the other the regular nodeapi we
know today.
<br>
<br>
Your suggestion (#4) has the advantage of collapsing everything in one
hook_nodeapi() though.<br>
</blockquote>
</body>
</html>