Yeah, that could be one thing that the ASP/ActiveX combo need to access the registry for.. but if he's replacing ASP with PHP and if the ActiveX control doesn't do anything he can't re-create in PHP, then there's no need to verify that anything relating to ASP or ActiveX is registered and genuine because it would have been replaced with a PHP alternative. I can't think of anything that a PHP app is going to need access to the registry for, so I'm trying to verify that there actually is a need for him to access the registry and/or use ActiveX via PHP. I'm guessing that he doesn't need to at all. -TG = = = Original message = = = Hi, Monday, July 30, 2007, 7:40:52 PM, you wrote: > I'm not sure that there's actually anything you'd need to access in > the server registry (and certainly no registry in Linux if you're > also transitioning from Windows to Linux). And depending on what the > ActiveX control your ASP pages accessed actually does, it may be > better to recreate it in PHP instead of trying to access ActiveX via > PHP. I've seen ASP components that required access to the registry in order to validate they were legal. I.e. the installer of the component wrote some serial number or something to the registry, which the ASP scripts checked. Nasty, but true. Just saying that he may well have a genuine need for it. Cheers, Rich -- Zend Certified Engineer http://www.corephp.co.uk "Never trust a computer you can't throw out of a window" -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php ___________________________________________________________ Sent by ePrompter, the premier email notification software. Free download at http://www.ePrompter.com. -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
