On 8/11/08, tedd <[EMAIL PROTECTED]> wrote:
> Now, do you agree with that?! Isn't that the SAME as what you said above?!
>
> Now, why not read the rest of what I wrote?
>
> Sometimes it's hard to get an idea across because some people refuse to
> read, but love to comment about the obvious.
Or th
At 12:19 PM -0700 8/11/08, mike wrote:
On 8/11/08, tedd <[EMAIL PROTECTED]> wrote:
Per Jessen:
I am sure you are smarter than this -- you're probably not understanding
what I am saying.
No, Per is correct.
PHP itself cannot access anything on the client. It is a server-parsed
language. T
At 2:07 PM -0500 8/11/08, Boyd, Todd M. wrote:
I think there is a difference in definition going on here.
-snip-
Todd:
I think you are right -- there must be some type of disconnect going
on here because it's obvious that php can receive data from
javascript.
It's also obvious that javascr
On 8/11/08, tedd <[EMAIL PROTECTED]> wrote:
> Per Jessen:
>
> I am sure you are smarter than this -- you're probably not understanding
> what I am saying.
No, Per is correct.
PHP itself cannot access anything on the client. It is a server-parsed
language. The client never executes PHP, period.
At 8:17 PM +0200 8/11/08, Per Jessen wrote:
tedd wrote:
> 2) "... there is NO way for PHP to access anything on the client."
<-- not true.
Statement 2 _is_ 100% true. Sorry, end of discussion for my part.
/Per Jessen, Zürich
Per Jessen:
I am sure you are smarter than this -- you're
pr
> -Original Message-
> From: Per Jessen [mailto:[EMAIL PROTECTED]
> Sent: Monday, August 11, 2008 1:17 PM
> To: php-general@lists.php.net
> Subject: RE: RE: [PHP] Re: PUT vs. POST (was: php File upload)
>
> tedd wrote:
>
> >>Todd, I just wanted to stres
tedd wrote:
>>Todd, I just wanted to stress that there is NO way for PHP to access
>>anything on the client. The way you wrote it, you sort of implied
>>that there might be other ways:
>>
>>"PHP by itself cannot access the local file system in a way that
>>allows ..."
>>
>>That's all.
>
> The ab
At 6:33 PM +0200 8/11/08, Per Jessen wrote:
Boyd, Todd M. wrote:
I had to use Java for the simple fact that PHP by itself cannot
access the local file system in a way that allows for the partial
loading of files.
Given that PHP doesn't run on the client, there is no way for
>> anything
Boyd, Todd M. wrote:
>>> I had to use Java for the simple fact that PHP by itself cannot
>>> access the local file system in a way that allows for the partial
>>> loading of files.
>>
>> Given that PHP doesn't run on the client, there is no way for
>> anything written in PHP to access anything on
> -Original Message-
> From: mike [mailto:[EMAIL PROTECTED]
> Sent: Saturday, August 09, 2008 2:47 PM
> To: Richard Heyes
> Cc: php-general@lists.php.net
> Subject: Re: [PHP] Re: PUT vs. POST (was: php File upload)
>
>
>
> On Aug 9, 2008, at 7:50 AM, &qu
> -Original Message-
> From: Per Jessen [mailto:[EMAIL PROTECTED]
> Sent: Saturday, August 09, 2008 9:09 AM
> To: php-general@lists.php.net
> Subject: RE: [PHP] Re: PUT vs. POST (was: php File upload)
>
> Boyd, Todd M. wrote:
>
> > I had to use Java for the
At 8:20 PM +0200 8/9/08, Per Jessen wrote:
tedd wrote:
> You see, anything that javascript can discover can be passed to php.
The limits are those limits imposed on javascript.
Ah, so you mean that _javascript_ can access something on the client -
very true, but javascript!=PHP.
Of cours
On Aug 9, 2008, at 7:50 AM, "Richard Heyes" <[EMAIL PROTECTED]>
wrote:
Given that PHP doesn't run on the client, there is no way for
anything
written in PHP to access anything on the client.
Wouldn't it be fun though if it could? :-)
--
Richard Heyes
http://www.phpguru.org
--
PHP Gene
tedd wrote:
> At 3:50 PM +0100 8/9/08, Richard Heyes wrote:
>> > Given that PHP doesn't run on the client, there is no way for
>> > anything
>>> written in PHP to access anything on the client.
>>
>>Wouldn't it be fun though if it could? :-)
>>
>>--
>>Richard Heyes
>
> In a round about way it
Except if paired with javadcript.
Luke Slater
Lead Developer
NuVoo
On 9 Aug 2008, at 15:09, Per Jessen <[EMAIL PROTECTED]> wrote:
Boyd, Todd M. wrote:
I had to use Java for the simple fact that PHP by itself cannot
access
the local file system in a way that allows for the partial loading o
At 3:50 PM +0100 8/9/08, Richard Heyes wrote:
> Given that PHP doesn't run on the client, there is no way for anything
written in PHP to access anything on the client.
Wouldn't it be fun though if it could? :-)
--
Richard Heyes
In a round about way it can, but it's limited.
You see, anyt
> Given that PHP doesn't run on the client, there is no way for anything
> written in PHP to access anything on the client.
Wouldn't it be fun though if it could? :-)
--
Richard Heyes
http://www.phpguru.org
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php
Boyd, Todd M. wrote:
> I had to use Java for the simple fact that PHP by itself cannot access
> the local file system in a way that allows for the partial loading of
> files.
Given that PHP doesn't run on the client, there is no way for anything
written in PHP to access anything on the client.
> -Original Message-
> From: mike [mailto:[EMAIL PROTECTED]
> Sent: Friday, August 08, 2008 4:36 PM
> To: Per Jessen
> Cc: php-general@lists.php.net
> Subject: Re: [PHP] Re: PUT vs. POST (was: php File upload)
>
> On 8/8/08, Per Jessen <[EMAIL PROTECTED]>
On 8/8/08, Per Jessen <[EMAIL PROTECTED]> wrote:
> I am not for or against either, I'm just looking for the right argument
> for PUT support as it seems to be lacking (and I've never found myself
> in a situation where PUT was the solution).
I need to accept files of various sizes - up to 2GB, ma
mike wrote:
> On 8/8/08, Per Jessen <[EMAIL PROTECTED]> wrote:
>
>> Same as POST then :-) (except for the resume bit).
>>
>> I still don't see much of a difference. It doesn't matter much to
>> me,
>> I'd just like to understand what the real difference is. Maybe I
>> need to go and read RFC26
21 matches
Mail list logo
