Ray,

Can't really comment on PHP as I've only taken a brief look, but what I can comment on 
is
server side JAVA - I've been using servlets & JSP commercially for the past year. IMHO 
you
wont go wrong if you choose JAVA especially when you are looking at DB interaction - 
beans
and interfaces lend themselves particularly well to this. As well as all this you get
session management, reusable libaries if written properly, tools like javadoc to 
generate
documentation from your code.
Only downside is server expense - I use Allaire JRun locally (win32)as both my
servlet/jsp/application engine and the basic web server that comes with it to develop
locally but have the luxury of our own server here (unix) to serve our stuff out to the
big wide world - if you dont have that luxury it could get pricy.

Mark


Raymond Smith wrote:

> Associates,
>
> I've been doing alot of research in what direction I would like to go next;
> in conjunction with the DynAPI.  While the API is wonderous for creating
> dynamic interfaces it needs a server-side partner in my mind to reach its
> full potential.
>
> Comparing ASP, JSP and PHP I've decided that LAMP (Linux, Apache, mySQL and
> PHP) tends to result in more robust client/server applications.  With PHP
> Zend boosted beating both in speed and performance and PHP appears to have
> allot of energy surronding it at this time.
>
> So, from that aspect, PHP wins.  Also there appears to be a very sizable
> family of "real" PHP initiatives on Source Forge to draw and learn from.
>
> But,...
>
> From my readings it's also apparent that JAVA is "king and master" of the
> Server Side Application if the JVM and runtime code is compiled properly.
> But, checking Source Forge for Java related projects creates a large list of
> mostly abstract and esoteric projects: not alot of meat on the bones from a
> "get things done" standpoint.
>
> Question is, what do you mavens of logical mayhem recommend as my next area
> of focus.  I am interested in developing some server-side applications that
> meld into the DynAPI interface on the client-side (yes, Pascal... be
> amazied).
>
> Java or PHP?
>
> Will learning PHP now be advantageous or detrimental to learning JAVA/JINI
> later?
> How does OOP in PHP compare to JAVA OOP?  I realize it lacks interfaces and
> solid abstraction.
> Why are most the PHP initiatives on Source Forge solid and down to earth
> while JAVA tends to be lofty and not very "real world" in nature?
>
> Looking for a little feedback here.
>
> Thanks,
>
> Ray "fear the rock" Smith
>
> _______________________________________________
> Dynapi-Dev mailing list
> [EMAIL PROTECTED]
> http://lists.sourceforge.net/lists/listinfo/dynapi-dev


_______________________________________________
Dynapi-Dev mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/dynapi-dev

Reply via email to