I agree that it should be possible to integrate PHP and Perl as portlet content sources. I don't see why they would need to be in the portal itself. Have PHP and Perl bindings to your portal's API, and have PHP authors write their apps (or integration glue code) as a set of cooperating portlets. This also allows developers of xxx, the as yet undiscovered latest and greatest language, to support their languages use in the portal by contributing language bindings for the API.


Luta, Raphael (VUN) wrote:


Big question here, what about PHP ? It's part of Apache and is also a very

popular choice for building portals. WSRP could definitely be used as a
bridge
between the Java and PHP world which would be a very good thing IMO.
Also consider Perl, etc...



I think that limiting the scope of portals.apache.org to Java and XML is too
restrictive. Although I admit that the communities mostly fall along
technology
lines right now, Portals address application integration issues within a
company
and should do their best to easily integrate many technologies. I think that

a common ground for all portal-related issues for any technology currently
represented in the ASF would be a very good move.






---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to