Re: [ciapug] File extension phpm

[laith <laith@xxxxxxxxxxxxxx>]

Don't know what it means specifically but most any file included by php 
will be treated as a php file regardless of extension (ie *.h, *.inc, 
haven't tried *.txt but I would not be surprised)

I don't think it is security unless the server is configed to no serve 
pages with that name as a direct call to an define type is usually sent 
to the browser and the browser will ask if you want to save if it does 
not have in-built handlers.

Laith

Carl Olsen wrote:
> I'm reading a book by Wrox, "Professional PHP5" and it uses a file extension
> of .phpm for several of the generic class files in Chapter 7.  I briefly
> brushed over chapters 1 and 2 and have been reading the rest of the chapters
> thoroughly (sometimes several times) and I haven't seen an explanation for
> why this file extension is necessary.  My web server isn't configured to
> recognize it, but it seems to run just fine as long as it's included in a
> page that has the normal .php file extension.  I'm thinking there must be
> some kind of security reason for this naming convention, but I can't figure
> out what it could be.  Does anyone know what it means?
>
> Another thing is that the first 6 chapters name all their class files with
> class.name_of_class.php and all their interfaces with
> interface.name_of_interface.php, but the ones with .phpm begin with the name
> of the class.  I suppose the .phpm might simply be a way of naming class
> files, but the book doesn't explain why these class files are named
> differently than the previous examples.
>
> Carl
> http://www.carl-olsen.com/
>
>
> _______________________________________________
> ciapug mailing list
> ciapug@xxxxxxxxxx
> http://cialug.org/mailman/listinfo/ciapug

_______________________________________________
ciapug mailing list
ciapug@xxxxxxxxxx
http://cialug.org/mailman/listinfo/ciapug