It looks like with the suggestions for XML-RPC calls would allow the modulecheck to be run with the cron hook. That way, everytime an admin looks at their modules page, it wouldn't be a call to
drupal.org, like an iframe would. Also, I'm not crazy about iframes, but I could in be a minority on that point.
On 11/19/06, Arnab Nandi <
arnab@arnab.org> wrote:What about simply having an iframe to
https://drupal.org/modulecheck/modulename, which returns a "You're
running the latest version" normally, or a button saying "click here
to upgrade" otherwise. The button essentially pionts to the changelog
/ install notes. (later, the button can point to the installer which
autoupgrades stuff).
-Arnab
On 11/19/06, Bèr Kessels <ber@webschuur.com> wrote:
> Op zaterdag 18 november 2006 18:41, schreef Karoly Negyesi:
> > In overall this solution is not enough because you many modules but by far
> > not all from contribs, so neither a per module feed or an eat-it-all feed
> > won't suffice. So definitely we need more code in project.
>
> I never said it would be enough. All I said is that, instead of talking for
> ages here about that utopian solution, then get into developing some whole
> new release-pushing-xmlrpc-system, we can offer a default RSS feed with block
> NOW.
>
> As in: now. Not something in some future after some unknown development cycle.
>
> Bèr
> --
>
> Drupal, Ruby on Rails and Joomla! development:
webschuur.com | Drupal hosting:
> sympal.nl
>
--
http://www.arnab.org