NYCPHP Meetup

[Phil Duffy]

I would like to express my appreciation to those in the NYPHP community (I
counted 13 responses) who responded to my question about a potential
successor to the Web.  It will take me a while to analyze these responses,
but the picture that was communicated was already useful to me.

 

I found the references provided by Dan Krook particularly useful for my
purposes:

 

Ajax and REST, Part 1: Advantages of the Ajax/REST architectural style for
immersive Web applications
http://www.ibm.com/developerworks/web/library/wa-ajaxarch/

 

Some more information about REST principles:

http://en.wikipedia.org/wiki/Representational_State_Transfer

 

 

My goal was to check my development direction, to be sure that I had not
become too attached to my current set of development tools only to find that
serious successors were already emerging and the work I was doing would soon
become obsolete.  My impression at this point is that my general direction
is reasonable, but requires some modification.

 

I should have described the application characteristics in more detail.
They must run over the Internet or a public equivalent.  They must blend
content management with data management.  Perhaps this is one of the reasons
that I seem to be encountering force-fits because as at least one
contributor to this discussion pointed out, the Web is stateless by design
intent.

 

If I have encountered some difficulties in dealing with statelessness for
the applications I am developing, it is not because of any difficulties I am
encountering in PHP.  I am impressed with PHP, but it is not the whole
picture.

 

Again, many thanks for the contributions that were made to this discussion.
They have saved me a great deal of research effort.

 

Phil Duffy

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.nyphp.org/pipermail/talk/attachments/20061020/d49bdde2/attachment.html>