While this is seriously cool stuff (and it does look like it is), I do see a
few snags with this kind of setup:
- Most people using the PHP code will have an existing infrastructure (most
likely apache, sometimes lighthttp etc) and do not want to run Jetty next to
it and take on a whole new chain to maintain.
- This looks like it runs PHP as a CGI .. slow being the keyword here (and
presumable also completely missing out on most of the php accelerating
possibilities such as ZendPlatform or APC)
- It wouldn't solve the issue that we want the URL's to be the same between
the Java and PHP versions, instead of creating 2 different ones (like you
suggested: /foo and foojava forinstance) so that all the examples and
javascripts work out of the box for both versions without any hacking to the
source.
So while indeed really cool stuff, it doesn't really look like a solution to
me at the moment
-- Chris
-----Original Message-----
From: Alejandro Rivero [mailto:[EMAIL PROTECTED]
Sent: Tuesday, March 18, 2008 21:25
To: [email protected]
Subject: Re: Social data request URL issue
2008/3/18, Alejandro Rivero <[EMAIL PROTECTED]>:
>
>
>
> so you can just rename the urlpattern socialdata to socialdatajava and
redirect the rest to a php service; I do not know yet how it works in
maven-jetty
Hmm not straightforward but it is described here.
http://docs.codehaus.org/display/JETTY/Jetty+and+PHP
