Re: API module namespace reservation

> MODULES ARE GOOD BECAUSE THEY ARE MODULAR. WHAT IS THE
ADVANTAGE OF PUTTING 6 INTO ONE?

THE EXISTENT MODULES DO NOT SHARE THE SAME DATA, ALTHOUGH
ALL OF THEM DEAL WITH THE SAME KIND OF INFORMATION. AFAIK,
MOST OF THEM IMPLEMENT THEIR OWN FORMS TO FETCH AND OUTPUT
SIMILAR DATA AND DO NOT INTEROPERATE WITH OTHER MODULES.
THUS, AN API(-LIKE) MODULE WOULD NOT ONLY RESERVE THE
GENERIC NAMESPACE BUT ALSO INTRODUCE A SHARED, EXTENSIBLE
DATASET.

THAT WAS THE GOOD NEWS. THE BAD NEWS IS, THAT THERE IS NO
CODE AND I WILL NOT HAVE TIME TO ACTUALLY DO SOMETHING
WITHIN THE NEXT WEEKS, WHICH IN TURN IS THE (HOPEFULLY
REASONABLE) CAUSE FOR MY QUESTION.

SUN

On 8/31/07, Daniel F. Kudwien <newsunleashedmind.com>
wrote:
> > Modules are good because they are modular. What is
the advantage of putting 6 into one?
>
> The existent modules do not share the same data,
although all of them deal with the same kind of information.
AFAIK, most of them implement their own forms to fetch and
output similar data and do not interoperate with other
modules. Thus, an API(-like) module would not only reserve
the generic namespace but also introduce a shared,
extensible dataset.


>From the description, the name 'drupal' comes to mind
for that module,
but it is already taken by a core module. 

Joking aside, not much can be said before hearing something
specific
about this module, anything.


> That was the good news. The bad news is, that there is
no code and I will not have time to actually do something
within the next weeks, which in turn is the (hopefully
reasonable) cause for my question.
>
> sun
>
>

This discussion is a bit pointless unless you can elaborate
on what
your new module might be doing.

As killes said - if you really think you want it, create a
project,
commit some skeleton/"hello world" code, and get
back to use when you
have something meaningful to share.

-Peter

On 8/30/07, Daniel F. Kudwien <newsunleashedmind.com>
wrote:
> > Modules are good because they are modular. What is
the advantage of putting 6 into one?
>
> The existent modules do not share the same data,
although all of them deal with the same kind of information.
AFAIK, most of them implement their own forms to fetch and
output similar data and do not interoperate with other
modules. Thus, an API(-like) module would not only reserve
the generic namespace but also introduce a shared,
extensible dataset.
>
> That was the good news. The bad news is, that there is
no code and I will not have time to actually do something
within the next weeks, which in turn is the (hopefully
reasonable) cause for my question.
>
> sun
>
>