Re: How kannel creates "cgi-bin" program to handle "http" requests

"Alejandro Guerrieri" <aguerrieri 'at' kannel.org> writes:

> I'm worried about backward compatibility. If it's removed and the cgi-bin URL
> no longer works, people will have to modify their applications to point to the
> new URL after the upgrade.

As long as Kannel offers a clear "what changed" document in new
releases, I don't see a problem. Well-designed applications don't
hardcode paths, or hardcode it so that modifications are possible
when needed. Well-behaving administrators/developers read what
changed documents, and test new releases of software on a
test/staging environment before going to production.

> IMHO the ideal approach would be to be able to maintain the "old" url as well
> (at least for the time being, maybe with a warning on the log files saying that
> it is deprecated).

It can be good to offer a backwards compatibility layer, but it
also means 1- extra time needed for Kannel developers 2- more
potential bugs (more lines of code = more bugs) 3- when this
backwards compatibility is abandoned in next-next release, you'll
still get angry users not reading documentation who will be
bitten anyway.

-- 
Guillaume Cottenceau