re: new module necessary?

I'll take a look. One thing that's required is that the link is periodically checked automatically. That's why janode was created (and Links module is not yet tagged DRUPAL-4-7 despite HEAD looking 4.7 compat).

However, if needs be, I'd be happy to contrib to maintaining the links module if it does what's needed. The "janode" was created as it was needed right now, specifically the 404 check. I'll have a closer look at the links module and decide which way to jump. On the face of it it looks good/right choice.

regards
--AjK

Since Link package never seems to come out of experimental stage I was happy to find your module. But... if you are already considering leaving it for Link package ("On the face of it it looks good/right choice"), should I really go for Janode? What will happen if you stop developing this module in favor of Link package? Will you then make a kind of conversion script from Janode to Link package? Any advice?

Afaict, the Links pakage is really a develpers "API" for links rather than supplying the end user with a "links experience".

Since the janode is now being activley used I will continue to support it.

What I mean't by "good/right choice" was that I may change the underlying code base to use the API at some future point if the defacto Drupal system adopts the links package "as the way to manage links" but what you get from "janode" right now will continue to be maintained by myself.

Since you and others are using it I'll support it.

Hope that answers your question.

best regards
--AjK

I'm chaning the status on this to "closed" as it hasn't produced much in the way of discussion and it appears there is a need for it (many using it).

--AjK