fletchsod

Gotcha! Just click that "Topic Solved" folder tab and voila! Thanks...

Thanks.. It does work now. I'm using this to update the received XML string before passing it on to MS-Access application and later the XML parser for the web browser. Scott P.S. How do I mark it as solved?

It's been a while I haven't use regular express, so I need someone with a fresh mind on this one. There is a SSN that is within the HTML tags or XML tags, so I only need to mask the SSN. There may be or may not be whitespace(s) between the SSN and the html/xml tags. IE --> <SSN>111-11-1111</SSN> --> <SSN> 111-11-1111</SSN> --> <SSN> 111-11-1111 </SSN> --> <SSN> 111-11-1111 </SSN> Whatever happens, I need it to become like this... IE --> <SSN>XXX-XX-1111</SSN> Thanks...

Ah! Found the forum posting that explained it all.. http://www.phpfreaks.com/forums/index.php/topic,183152.0.html http://www.phpfreaks.com/forums/index.php/topic,181773.0.html I didn't think it was recent. I figured it was like 6 months ago or something. Sorryabout that...

I was surprised about the changes of the website. So, I read the "PHPFreaks Site Feedback" and understood what's happening. So, I have one question. I haven't search or read the old posting, since I don't think I would be able to find it, so I made a posting here. Sorry if I'm a bit stumped or something. Is there a link to tutorial or sample project someone had freely provided to us? (So I can browse through to see if there's something I can use). Thanks, FletchSOD

Interesting... I have read reports that some php developers had successfully destory the tmp session file via "session_destory()" command...

Everytime the session_destory() is issued, the /tmp/sess_*** files with the same session_id() are still there... Why does it not get destroyed?? How do we properly destroy it? I sometime wonder about trying to destroy the sessions in the memory as well (via session.save_handlers = "mm")... This is what I get... --snip-- Warning: Session object destruction failed in php_library.inc on line 126 --snip-- Thanks, Scott

Since the "session_write_close()" end the session after it force a wait-state as to finish writing the session data. So, is there an alternative function that would force a wait-state while data is still writing to session WITHOUT ending a session? Thanks...

[!--quoteo(post=374803:date=May 17 2006, 05:25 PM:name=toplay)--][div class=\'quotetop\']QUOTE(toplay @ May 17 2006, 05:25 PM) [snapback]374803[/snapback][/div][div class=\'quotemain\'][!--quotec--] Oh, yeah cool. I completely forgot about memory based session support in PHP (under Unix/Linux). I've used the "user" option to write sessions to MySQL instead of PHP flat files. But you're the first I've heard of needing memory based. Good luck and happy coding. [/quote] Yea, I'm using AIX on this one... By the way, it's all new to me but I did read recently that the memory based session is already built-in by default for Windows while it's not by default for Unix/Linux. Weird. [img src=\"style_emoticons/[#EMO_DIR#]/smile.gif\" style=\"vertical-align:middle\" emoid=\":smile:\" border=\"0\" alt=\"smile.gif\" /]

[!--quoteo(post=374753:date=May 17 2006, 01:49 PM:name=toplay)--][div class=\'quotetop\']QUOTE(toplay @ May 17 2006, 01:49 PM) [snapback]374753[/snapback][/div][div class=\'quotemain\'][!--quotec--] Ram is not permanent especially if the server goes down or has to be rebooted. I'm sure they'd allow you to use sessions (disked base solution) if you have the data encrypted. See: [a href=\"http://us2.php.net/manual/en/ref.sem.php\" target=\"_blank\"]http://us2.php.net/manual/en/ref.sem.php[/a] (not available for Windows) [a href=\"http://us2.php.net/manual/en/ref.shmop.php\" target=\"_blank\"]http://us2.php.net/manual/en/ref.shmop.php[/a] [/quote] THe data does not need to be permament. It's only as good as the 15 minutes idle-timeout. Yea, I can use the session but it can not store the data to the disk at all. Encrypted or not, storing bytes to the disk would be a violation anyway. I just recently found some information. Took me a while to understand the confusion due to lack of documentation. A link to Zend's website at "http://www.zend.com/zend/tut/session.php#storage" and look under the "Storage Modules" section halfway down on the webpage. Again, I got this info from "http://www.onlamp.com/pub/a/php/2001/04/26/sessions.html" under the configuration section that explain it in more detail. So, that got me thinking and I spend some time searching at php.net website for answers and it wasn't until I found one at "http://www.php.net/manual/en/ref.session.php" under the "Installation" section that I overlooked. Kind of hard to read but very easy to overlook when searching in vain for some answer. I'm glad I finally found something that can be of a use. I would like to go with the PHP's Session feature instead of the 3 parts, "Semaphore, Shared Memory and IPC Functions"... Not that I don't want to use those three parts but I'm afraid it would be a pain to write a script because it is all new to me and act like I'm crossing my finger hoping for the best and that nothing goes wrong in the long run. For one of you who are interesting in learning how to accomplish that (PHP's Session) then a good documenation for compiling one (How-To) is at "http://www.zend.com/tips/tips.php?id=164&single=1" I just discover it from Google Search while looking for more information about Session and Shared Memory not related to this web link. I'm thinking of going to file a PHP bug to get somebody to update the PHP's Session documentation becuase it's not a well and clear documentation. Thanks for all of your time and suggestion. I appreciated it... Edited: PHP Bug #37484 (Sorry if my comments there is sloppy 'cuase it's all I think of).

Hi fellas!! I'm a little bit frustrated because I found no information on the Internet to help me out. What I need is a way to store the PHP array data into the RAM memory and come back to retreive it at a later time. A lot like the C/C++ language... Like 1st web page, store it there then any other web pages, retrieve it. This can be done by saving the known memory address for later use. I can not use the PHP's session because it store the data to a temporary file on the hard disk because it would have been illegal to do so. (It's because of the law - Fair Credit Reporting Act and of the agreement we made with Equifax, Experian and Trans Union). But we're allow to store them in the RAM because the information is permamently stored there and it seem that nothing can retrieve it by a non-php process. I can't use the database either. What do I need to do? Thanks, FletchSOD

Um, didn't know about this... --snip-- Please note that mod_ssl is only for Apache 1.x. Apache 2.x does not use mod_ssl -- SSL is built into Apache 2.x. --snip-- I might would be in for a surprise if something else is new.... Edit: Saw other post via Google which said Apache 2.x doesn't need one because it have a built-in ones...

Is there something I should know about on upgrading to Apache 2.x with PHP 5.1.x from Apache 1.3.x with PHP 4.3.6?? I know PHP 5.1.x isn't really that out yet but it would be in January when I start migrating the large website over. Will there be performance issues? Problem that I should be aware of? I just wanna make sure because Apache/PHP is not the only thing I will be upgrading with. I'll be switching the database from DB2 to MySQL as well. It's a lot of work for a large website here. :-) FletchSOD