|
|
Posted by Jerry Stuckle on 09/20/06 01:41
bvdb wrote:
> Hello,
> Jerry Stuckle wrote:
>
>>No, I'm trying to direct you to the best possible resource for your
>>question. But you are too thick-skulled to understand it.
>
>
> It's not yours or anybodys job to "direct" anybody else to something.
> The idea of a newsgroup is: If you have something to say to answer the
> question, say it, if not, stay quiet.
>
No, it's not my "job". However, I do try to help people. If it's
something pertinent to this group and I can handle it, I do. If it's
pertinent to this group and I can't, I let someone else. And if there
is a better group to ask the question in, I try to steer the person that
way, even if he being an arrogant asshole.
>
>>No, it's not "tightly connected to PHP". This is strictly HTML and
>>browser behavior.
>
>
> Nonsense, obviously you have not read my description.
> If it was pure HTML, the same link would fetch the same content and
> thus render the same page.
> The whole question only makes sense with a server application.
>
Not at all. Something on the server that is completely independent
(i.e. a cron job that runs every 10 seconds) can replace the HTML pages
between requests from the browser. The same link would retrieve
different content every 10 seconds. But it would be static HTML.
>
>>This would be exactly the same if the header were
>>generated in PHP, Perl, VBScript
>
>
> Okay. So now it's PHP.
>
Right. It's generated by PHP. But the problem is not a PHP problem.
>
>>.. or even HTML itself.
>
>
> HTML cannot generate HTTP-headers like the header()-function does.
> You don't know what you're talking about.
>
Actually, I do. Apache/IIS can and does generate EXACTLY the same type
of headers as PHP does. To an IP trace sometime and figure it out. The
only difference is that these headers are preset in the httpd.conf file.
But I doubt you know anything about that.
Unlike you, I've been dealing with webserver intimately for around 15
years - including internals. I know *exactly* what I'm talking about.
>
>>No, it was not a good choice. Look how many answers you've gotten.
>
>
> The thread was poisoned by an arrogant wannabe.
> So, sad enough, we can merely expect people with a constructive
> attitude to join in (any more).
>
Not at all. It was someone who didn't know what newsgroup to ask it in.
There is nothing stopping anyone else from responding.
I'll expect the apology when you get your answer and find it's not a PHP
problem at all. But I know I won't get it. Guys like you never do.
Go ahead - spin your wheels. I don't need to put up with your asinine
abuse. So much for trying to help a complete idiot.
--
==================
Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
jstucklex@attglobal.net
==================
Navigation:
[Reply to this message]
|