virgo27;10998153 wrote:But when the client's "SO" file is loaded, it says "not a valid "SO" file. Now the client says that the file works fine on their end.
Can you query the client to see exactly which version of PHP they're using that successfully loads the .so file? This is important; I don't believe you can compile an extension against PHP 5.2 source and then give the compiled .so file to someone running PHP 5.3 and expect it to work.
virgo27;10998153 wrote:Kindly also elaborate "SO" files in simplest terms
These files are "dynamically linked shared object libraries." If you're more familiar with Windows applications, then the ".so" files are analogous to ".dll" files on Windows. Basically, they're little modules that can't actually be directly executed by are instead meant to be "included" by other compiled applications that will use function calls defined by the .so/.dll file in order to use the "module" or functionality that the file provides.
virgo27;10998153 wrote:are they only developed using c/c++ or any other language can also be used to develop "SO" files.
My experience with compiled languages (such as C/C++; as opposed to "interpreted" languages like PHP, Python, etc.) is limited to mostly C/C++, but no, you could certainly create your own '.dll' file on Windows using something like C# instead.
virgo27;10998153 wrote:Also can the same "SO" file be used via jsp and php?????
The library/object is going to have a defined API to call into it and use it - hence why you've got all sorts of PHP_METHOD(), zend_entry, etc. macros being used all over the place in that tutorial you linked to. Anything that expects that API format can link to and use the .so module.
virgo27;10998153 wrote:And is there any possibility that an "SO" file is working with jsp and not working with php?????
Depends what you mean by "working with jsp" since JSP is a Java technology and not a software application.
