We should come up with some specification for the component, including
the methods and properties. Then, it could be created for different
environments, but work essentially the same. That way, people could
help work on the specific language that they know the best.
--
// Robert Rainwater
On 2/14/2001, 2:09:52 PM EST, Doug wrote about "[Dynapi-Dev] serious, ... really!":
> What about those who don't use unix?
> How about a perl based DynServer component?
> We could implement Server-side File i/o, as well as a Perl based Database..
> To name a couple of things
> ----- Original Message -----
> From: "Raymond Smith" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Tuesday, February 13, 2001 4:29 PM
> Subject: [Dynapi-Dev] serious, ... really!
>> 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
> ---
> Outgoing mail is certified Virus Free by AVG Free Edition
> http://www.grisoft.com/html/us_index.cfm
> Checked by AVG anti-virus system (http://www.grisoft.com).
> Version: 6.0.231 / Virus Database: 112 - Release Date: 2/12/01
> _______________________________________________
> Dynapi-Dev mailing list
> [EMAIL PROTECTED]
> http://lists.sourceforge.net/lists/listinfo/dynapi-dev
----------------------
DynAPI Snapshots: http://dynapi.sourceforge.net/snapshot/
DynAPI Homepage: http://dynapi.sourceforge.net/
_______________________________________________
Dynapi-Dev mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/dynapi-dev
