Re: Custom headers - bug or feature

Rudy Taraschi wrote:

> Hi folks,
> 
> Right now, if I create a custom header that is the same as one of the
> slrn-generated headers, I end up with two copies of said header - the
> generated one and mine.  That doesn't seem right.

According to my reading of the RFCs, it's not even clear which version 
of the header should take priority - the first or the last - and that 
could cause significant problems.

> My opinion is that the custom header should over-ride the
> auto-generated one.

Not for essential headers, surely?

> Less desirable (to me) but equally correct would
> be for the auto-generated one to have priority.  Either way, I don't
> see duplicate headers as the proper behaviour.

Neither do I, but my solution would be to prevent users from adding 
headers that conflict with standard headers. Given a minimal amount of 
technical skill, it's already easy to change headers after slrn has 
generated them, but it shouldn't be made *too* easy.

> John: would you like me to take a stab at patching this (which could
> take awhile), or are you happier just to leave it on your queue?

I'd rather such a patch were not made publicly available.

-- 
PJR :-)

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july