php-general Digest 31 May 2011 10:13:41 -0000 Issue 7336
Topics (messages 313246 through 313258):
Re: iPhone sadness
313246 by: jean-baptiste verrey
313247 by: Tim Streater
313248 by: Micky Hulse
313251 by: Geoff Shang
313252 by: Tim Thorburn
313253 by: Alexis
https help
313249 by: Negin Nickparsa
313250 by: admin.buskirkgraphics.com
313255 by: Negin Nickparsa
313256 by: Negin Nickparsa
313257 by: viraj
apache or php limit?
313254 by: Peet Grobler
Why Is the Zend debugger this too slow?
313258 by: Ali Asghar Toraby Parizy
Administrivia:
To subscribe to the digest, e-mail:
[email protected]
To unsubscribe from the digest, e-mail:
[email protected]
To post to the list, e-mail:
[email protected]
----------------------------------------------------------------------
--- Begin Message ---
I like how people just like to complain about everything^^
But as the debate is raging I had a look over internet and
http://www.caliburn.nl/topposting.html gave the best argument ever :
we read from *top* to *bottom *so top posting makes you read useless
information^^
Don't worry, be PHaPpy!
On 30 May 2011 19:01, Lester Caine <[email protected]> wrote:
> Ashley Sheridan wrote:
>
>> And, BTW, this bottom posting has started just two or three years ago
>>> >when Thunderbird came in place.
>>>
>> Erm, bottom posting has been the standard since day 1 until Microsoft came
>> along and changed it with Outlook. Most people who use Windows tend not to
>> change basic settings from their defaults.
>>
>
> Exactly ...
> I've email archives going back to 1992 and ALL of the early stuff is nicely
> formatted with in-line and bottom posted expansion. I've actually been
> editing things I would like to keep to put some sense back into the archive
> - but on the most part just trimming reams of unnecessary repeated sigs
> where people have not even bothered looking at what they quoted! I've got a
> nice module on my php client management system that trims stuff
> automatically for me when I'm uploading old messages.
>
>
> --
> Lester Caine - G8HFL
> -----------------------------
> Contact - http://lsces.co.uk/wiki/?page=contact
> L.S.Caine Electronic Services - http://lsces.co.uk
> EnquirySolve - http://enquirysolve.com/
> Model Engineers Digital Workshop - http://medw.co.uk//
> Firebird - http://www.firebirdsql.org/index.php
>
> --
> PHP General Mailing List (http://www.php.net/)
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>
--- End Message ---
--- Begin Message ---
On 30 May 2011 at 19:07, jean-baptiste verrey <[email protected]>
wrote:
> I like how people just like to complain about everything^^
> But as the debate is raging I had a look over internet and
> http://www.caliburn.nl/topposting.html gave the best argument ever :
> we read from *top* to *bottom *so top posting makes you read useless
> information^^
Actually, if you're trying to make *that* argument, then in fact the reverse is
true: *bottom* posting makes you read useless information - because all the
stuff I see first I've seen before. It's worse on Usenet in fact because there
are some ***** who never learnt to snip. So I have to scroll down two pages
just to see their one-liner. Sometimes that's a problem here, too.
--
Cheers -- Tim
--- End Message ---
--- Begin Message ---
The WebDesign-L has been around since early 1997... For as long as I
can remember, the policy (on all list-servs I post to) has been "no
top posting" and "trim quotes".
Here's WD-L's policy page:
<http://webdesign-l.com/policies/>
Lot's of great info there...
Under the "Message Body" heading:
[[
Do not top-post; write your reply below the quoted portion(s) of the
message to which you are replying.[Hide]
Putting your reply above a quoted message makes it difficult for
others to know exactly which point you are replying to. Quoting
portions of the preceding message above your reply helps others follow
along.
Trim your replies. Avoid quoting the entire preceding post, and take
care not to include the list footer
When replying, quote only what is needed for context. While most
people will not remember the previous message verbatim, you should
assume that those interested have been following the thread and do not
need to reread the previous post to understand yours. Quoting the
entire message wastes bandwidth, annoys members, and makes the digest
hard to read.
Avoid over-trimming.
Include names, but not the email addresses, of persons being quoted,
relevant URLs, and enough of the original post so that readers know to
what and whom you’re responding. If you’re responding to several
posts, or to the thread in general, please say so.
]]
I personally try to follow all the rules on that page for all of the
list-servs I am a member of.
For personal e-mails, that's a different story... I have found that
most folks, that don't use list-servs, don't get inline replies and
bottom posting (with quote above reply).
Cheers,
Micky
--- End Message ---
--- Begin Message ---
On Mon, 30 May 2011, Andre Polykanine wrote:
most of you post your messages *after* the quotes. It's
really not comfortable: I use screenreading software here and I need
to scroll with my down arrow key before I see the actual message.
I use screen reading software as well and prefer bottom-posting. Of
course, those who quote an entire message (or messages) before their post
should be shot, but thankfully this is a minority of people.
Since we're all pitching in with our arguments for top/bottom posting,
I'll briefly state mine:
1. Bottom (or at least "not top") posting allows you to interleave your
responses amongst the quoted text. This makes it a lot easier to know
what is being responded to, and actually also makes it a lot more likely
that all points that need answers will actually be answered.
2. Particularly if #1 is followed, quoted material more often than not
tends to be trimmed to what is relevant. Top-posting not only usually
results in the entire message being quoted, but often the entire thread
right back to the beginning (or at least back to whoever bottom-posted
last on it). This can cause very large messages fairly quickly,
especially if combined with HTML mail (don't get me started on *that*
one).
Unfortunately, Outlook Express (and perhaps others) seem to actively
discourage doing the right thing. One reason is that at least in Outlook
Express, it's impossible to set different quoting settings for replies and
forwards. So you either end up with forwards with all quoted lines (very
annoying to listen to I assure you), or replies where it's impossible to
tell what's quoting and what's new text (unless you're sending as HTML
mail of course).
And of course, the single reason (IMHO) why it's likely more people
top-post - it's less work.
Geoff.
--- End Message ---
--- Begin Message ---
Is there any way that we could simply ban these ridiculous top-posting
vs bottom-posting threads that seem to come along every few weeks? I
frankly don't care where a person writes a reply - I'm quite able to
scan through an email message to find the relevant points regardless.
Maybe we could add a [posting position rant] tag onto emails that
discuss this topic so those of us who couldn't care less could simply
have them directed straight to the trash can?
--- End Message ---
--- Begin Message ---
Here here Tim, I thought this was meant to be a PHP list.
I can remember when it first started, no moaning about this or that,
just pure PHP, and no sarcastic comments either, bring back the good old
days :)
Alexis
On 30/05/11 17:04, Tim Thorburn wrote:
Is there any way that we could simply ban these ridiculous top-posting
vs bottom-posting threads that seem to come along every few weeks? I
frankly don't care where a person writes a reply - I'm quite able to
scan through an email message to find the relevant points regardless.
Maybe we could add a [posting position rant] tag onto emails that
discuss this topic so those of us who couldn't care less could simply
have them directed straight to the trash can?
--- End Message ---
--- Begin Message ---
hi all,
I want to write an application that can be logged to yahoo.com using https
protocol
Would you please put me some suggestions and advices?
if ($_SERVER['SERVER_PORT'] != 443) {
header("Location: https://".$_SERVER['HTTP_HOST'].$_SERVER['REQUEST_URI']);
}
--- End Message ---
--- Begin Message ---
Negin,
That is pretty vague.
More details please
Richard L. Buskirk
Senior Software Engineer/Systems Administrator
You can't grow your business with systems that are on life support...
-----Original Message-----
From: Negin Nickparsa [mailto:[email protected]]
Sent: Monday, May 30, 2011 4:04 PM
To: [email protected]
Subject: [PHP] https help
hi all,
I want to write an application that can be logged to yahoo.com using https
protocol
Would you please put me some suggestions and advices?
if ($_SERVER['SERVER_PORT'] != 443) {
header("Location: https://".$_SERVER['HTTP_HOST'].$_SERVER['REQUEST_URI']);
}
--- End Message ---
--- Begin Message ---
I need to create a login page with HTTPS to yahoo
Do I have to have a valid certificate?
I have not trust certification centre, so before anything under HTTPS will
be shown up, the window will come with information: valid certificate: yes,
valid domain: yes, valid authority for SSL key: no.
am I right?
<?php
//if not on HTTPS
if(empty($_SERVER['HTTPS'])) {
//build link to https page; protocol, server and current script path
$url = "Location: https://www.yahoo.com/";;
//addy querystring, if appropriate
if(count($_GET) != 0) {
$url .= "?";
foreach($_GET as $key => $value) {
$url .= "$key=$value&";
}
}
//send permanent move redirect
header($url, true, 301);
}
?>
but it goes to http://www.yahoo.com
--- End Message ---
--- Begin Message ---
it is the output:
http://www.yahoo.com/?s=https
can i force it to show me
https://www.yahoo.com
?
--- End Message ---
--- Begin Message ---
yahoo don't have ssl enabled on all their content it seems.
http://privacy.yahoo.com/privacy/us/security/details.html
~viraj
On Tue, May 31, 2011 at 11:11 AM, Negin Nickparsa <[email protected]> wrote:
> it is the output:
> http://www.yahoo.com/?s=https
>
> can i force it to show me
> https://www.yahoo.com
>
> ?
>
--- End Message ---
--- Begin Message ---
Hi there, new to this list.
I have a problem I can't seem to figure out. Here goes.
PHP page has 100s of textboxes on it. Submit on the development machine,
everything works as expected. Submit on live machine - only part of the
$_POST variables are there. The script doesn't stop executing - it
executes just fine with the limited data.
I've checked:
- post_max_size - more than enough (8M). Increased to 512M and
re-tested, this is definately not the problem.
- memory_limit - same thing (increased from 128M to 512M)
- apache2.conf is the same on both hosts (except for ServerName,
etc.
- php.ini is the same on both machines (except for debugging information
turned on on development machine).
- I enabled debugging and logging on the live machine, but there's
nothing in the logs.
Can anyone point me in any direction please. It boggles the mind that
the exact same script works fine on one machine, but not the other,
given that apache and php configs are the same.
flu:~# apache2 -v
Server version: Apache/2.2.16 (Debian)
Server built: Mar 22 2011 20:56:31
flu:~# php -v
PHP 5.3.3-7+squeeze1 with Suhosin-Patch (cli) (built: Mar 18 2011 17:22:52)
Copyright (c) 1997-2009 The PHP Group
Zend Engine v2.3.0, Copyright (c) 1998-2010 Zend Technologies
with Suhosin v0.9.32.1, Copyright (c) 2007-2010, by SektionEins GmbH
flu:~# cat /proc/version
Linux version 2.6.26-2-686 (Debian 2.6.26-26lenny1) ([email protected])
(gcc version 4.1.3 20080704 (prerelease) (Debian 4.1.2-25)) #1 SMP Thu
Nov 25 01:53:57 UTC 2010
flu:~#
If this is the wrong place to ask please point me in some direction.
--- End Message ---
--- Begin Message ---
Hi
I've installed pdt and zend debugger.
But when I start debugging as web page it takes a long time to start
the debugging for each page. Browser remains in waiting status for
farther than 10 or 20 seconds before loading a page. But after that
debugging seems to be comfortable. I think there is a problem with
some initializations!
I use widows7 and wamp. eclipse helios. php version 5.2.4 and zend plugin 4.2.x
--
Ali Asghar Torabi
--- End Message ---
