On Thu, 27 Jan 2000, Leon Atkinson wrote:
> I did intend for the servlet and PHP versions to be able to share a
> database...in case a site ever wanted to migrate to another platform. We
> did make it a little harder to do that when we used PHP's serialization
> for baskets. And maybe no one would ever want to migrate, anyway.
Why exactly would people want FreeTrade in different languages? FreeTrade
seems like more of a foundation for a new site as opposed to something you
would add to an existing one (it's got a great plan to it, but it does NOT
play nicely with any other way of putting a site together). So I can't see
a lot of situations where you could reuse a lot of your existing
java/php/asp code without heavy modification (likely similar to the effort
it would take to port the logic from a different language). I actually found
porting my old perl script logic to FreeEnergy easier than integrating other
existing php code into it cause I *had* to start fresh with it.
The downside of multiple concurrent languages is that any feature/change has
to be implemented in all the languages to maintain compatibility, forcing us
into the lowest common denominator, and not letting us use the unique
features of ANY of the platforms. And if we aren't maintaining
compatibility, then what's the point?
Are the java-based options really THAT much better? If so, then should the
whole project move to be java-based? If java DOESN'T provide significant
benefits, then does focusing on only php (so we can use it's unique
features) make the most sense?
- Isaac =)
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Site: http://www.working-dogs.com/freetrade/
Problems?: [EMAIL PROTECTED]
