php-general Digest 17 Sep 2009 17:56:19 -0000 Issue 6344

Topics (messages 298105 through 298113):

Re: APC - Upload progress problem. apc
        298105 by: Jim Lucas
        298106 by: Ben Dunlap
        298107 by: Phred White

ie6 "memory could not be read" help!
        298108 by: Shelley
        298109 by: Ashley Sheridan
        298113 by: Philip Thompson

Validation XHTML code and repairing broken one
        298110 by: Dušan Novaković
        298111 by: Bob McConnell
        298112 by: Al

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 ---
Phred White wrote:
He's baaaaack...

Well folks..

The good news is that APC and my upload progress is working! : )

The bad news is, ...kind of working.  : |

It does exactly what I want, but at 1 hour of progress-barring, it stops. I.e., APC stops returning a response for the given key. Whether the connection has allowed 100MB, 500MB or 1GB. The file actually continues to upload, for hours if necessary, and eventually gets there.

APC provides a sort of management page that lets you look at the APC status, including a listing of "User Cache Entries" which includes any still-valid upload keys, and any keys created via apc_add(). This listing includes a Timeout value, which is "none" for the apc_add keys and 3600 for the upload keys. Somewhat suspicious, I'd say, since the keys stop being working after 1 hour of use.

APC lets you set a number of timeout values: apc.gc_ttl, apc.user_ttl, apc.ttl. I have set all of these to be gianormous, but the upload key timeout value never changes.

I can't believe that this is an inherent limitation, or nobody would be using this. The Google claims people are using this for big uploads, so I should be able to. I have looked through Apache/unix to see if this limit refers to something set deeper in the system, but everything that I know of that I can loosen up, I have.

Any ideas?

Thanks, Phred


Are you using SESSIONS or COOKIES at all in this application?

If so, could it possibly be related to one or the others timeout configuration?

--
Jim Lucas

   "Some men are born to greatness, some achieve greatness,
       and some have greatness thrust upon them."

Twelfth Night, Act II, Scene V
    by William Shakespeare

--- End Message ---
--- Begin Message ---
> upload keys, and any keys created via apc_add(). This listing includes a
> Timeout value, which is "none" for the apc_add keys and 3600 for the upload
> keys. Somewhat suspicious, I'd say, since the keys stop being working after
> 1 hour of use.
>
> APC lets you set a number of timeout values: apc.gc_ttl, apc.user_ttl,
> apc.ttl. I have set all of these to be gianormous, but the upload key
> timeout value never changes.
>
> I can't believe that this is an inherent limitation, or nobody would be
> using this. The Google claims people are using this for big uploads, so I

I've just had my first glance at the APC source code, so I could be
misreading something, but it appears that 3600 was hardcoded in until
about 3 weeks ago.

Here's the trunk commit that seems to have made that value configurable:

http://svn.php.net/viewvc?view=revision&revision=287534

And there's a reference to a PECL bug in the commit message:

http://pecl.php.net/bugs/bug.php?id=16717

I have no idea when this change will trickle through to a production
build -- or if it already has, but I suspect not, because the
hardcoded 3600 was still present in the latest available source code
tarball at http://pecl.php.net/get/APC

Ben

--- End Message ---
--- Begin Message ---

On Sep 17, 2009, at 12:27 AM, Ben Dunlap wrote:

upload keys, and any keys created via apc_add(). This listing includes a Timeout value, which is "none" for the apc_add keys and 3600 for the upload keys. Somewhat suspicious, I'd say, since the keys stop being working after
1 hour of use.

APC lets you set a number of timeout values: apc.gc_ttl, apc.user_ttl,
apc.ttl. I have set all of these to be gianormous, but the upload key
timeout value never changes.

I can't believe that this is an inherent limitation, or nobody would be using this. The Google claims people are using this for big uploads, so I

I've just had my first glance at the APC source code, so I could be
misreading something, but it appears that 3600 was hardcoded in until
about 3 weeks ago.

Here's the trunk commit that seems to have made that value configurable:

http://svn.php.net/viewvc?view=revision&revision=287534

And there's a reference to a PECL bug in the commit message:

http://pecl.php.net/bugs/bug.php?id=16717

I have no idea when this change will trickle through to a production
build -- or if it already has, but I suspect not, because the
hardcoded 3600 was still present in the latest available source code
tarball at http://pecl.php.net/get/APC

Ben

Ben:
Thank you so much, I felt like I was on crazy pills!

I was afraid it was a bug. I have generally just used whatever is at whatever host, until this project, and didn't really think something so glaring could be in there. WTF!

So, it seems like it would be pretty straight forward to fix this, if I was willing to run on a custom version until this fix is released. Do people do that? What do you think?

The alternative is starting over with python or perl. Sheesh!

Phred

--- End Message ---
--- Begin Message ---
Hi all,

With IE6,

After the pages i developed was loaded, there seems to be no problem,
but when you then click a link, refresh the page, etc. it shows "memory
could not be 'read'" error message.

However, when you load other sites, google.com, for example, there is no
such problem.

Anybody knows how to fix this problem?

Any help is appreciated & thanks in advance.

-- 
With best regards,
Shelley Shyan
http://php42.com
http://phparch.cn

--- End Message ---
--- Begin Message ---
On Thu, 2009-09-17 at 16:41 +0800, Shelley wrote:
> Hi all,
> 
> With IE6,
> 
> After the pages i developed was loaded, there seems to be no problem,
> but when you then click a link, refresh the page, etc. it shows "memory
> could not be 'read'" error message.
> 
> However, when you load other sites, google.com, for example, there is no
> such problem.
> 
> Anybody knows how to fix this problem?
> 
> Any help is appreciated & thanks in advance.
> 

http://support.microsoft.com/kb/899811

first result from a Google search

Thanks,
Ash
http://www.ashleysheridan.co.uk




--- End Message ---
--- Begin Message ---
On Sep 17, 2009, at 4:04 AM, Ashley Sheridan wrote:

On Thu, 2009-09-17 at 16:41 +0800, Shelley wrote:
Hi all,

With IE6,

After the pages i developed was loaded, there seems to be no problem,
but when you then click a link, refresh the page, etc. it shows "memory
could not be 'read'" error message.

However, when you load other sites, google.com, for example, there is no
such problem.

Anybody knows how to fix this problem?

Any help is appreciated & thanks in advance.


http://support.microsoft.com/kb/899811

first result from a Google search

Thanks,
Ash

Since this post is not PHP-related, I'll continue the trend. Are people still using IE6? In sites I design, I prevent the user from viewing it. If they're still on IE6, I don't want them to use my sites.

Cheers,
~Philip

--- End Message ---
--- Begin Message ---
Hello,

I have few questions about validation XHTML and repairing if it's
broken. The problem is that I have some, for example HTML code (simple
web page) and want to load that page to DOMDocument and than make
something of it. That part works perfect, but if there is unclosed tag
or something like that when I try to load that page I get an error
because now that code is not valid. So my question would be, is there
some way that I could build some script in php that would run thought
that page and check if it's valid or not, and if it's not than try to
repair it. Something that you have in all tools, for example Eclipse,
NetBeans, etc. If anyone have any idea, please help me, because I'm
stuck in here :-(

Regards,
Dusan

-- 
made by Dusan

--- End Message ---
--- Begin Message ---
From: Dušan Novakovic

> I have few questions about validation XHTML and repairing if it's
> broken. The problem is that I have some, for example HTML code (simple

I use a Firefox plug-in called HTML Validator and then edit the source code for 
the pages in NetBeans. It uses either Tidy or the W3C SGML parser or both, your 
choice. Unfortunately it relies on some MS-Windows applications so it won't 
install on Linux. So I can use it on pages I build at work, but not on my 
personal stuff at home.

Bob McConnell

--- End Message ---
--- Begin Message ---



Hello,

I have few questions about validation XHTML and repairing if it's
broken. The problem is that I have some, for example HTML code (simple
web page) and want to load that page to DOMDocument and than make
something of it. That part works perfect, but if there is unclosed tag
or something like that when I try to load that page I get an error
because now that code is not valid. So my question would be, is there
some way that I could build some script in php that would run thought
that page and check if it's valid or not, and if it's not than try to
repair it. Something that you have in all tools, for example Eclipse,
NetBeans, etc. If anyone have any idea, please help me, because I'm
stuck in here :-(

Regards,
Dusan


I spent some time on this issue because I have several applications where users enter text that must be later displayed as valid XHTML on a webpage.

I've found Tidy [a PHP extension] is the best and simplest solution. [I know about JAVA based, client-side scripts; but, don't like having to be constantly updating them for bug fixes, security patches and IE changes, etc.]

However, my applications are designed to run on shared hosts and many web hosts won't install it for them. So, I've had to script my own XHTML validator. You are welcome to use the functions, just ask. I must warn you, much of the code uses regex expressions; so, if you are not familiar with regex, I'd advise not using them.

Al.........

--- End Message ---

Reply via email to