83
edits
No edit summary |
No edit summary |
||
| Line 25: | Line 25: | ||
Sticking with PHP seems to make the most sense at this time. We have that skill set (both on the development and systems side) and the alternatives are not particularly attractive. We considered both Perl and Java but decided against both at this time. The existing UMO service is currently scaling quite well with over 3 million unique clients a day across 3 servers. | Sticking with PHP seems to make the most sense at this time. We have that skill set (both on the development and systems side) and the alternatives are not particularly attractive. We considered both Perl and Java but decided against both at this time. The existing UMO service is currently scaling quite well with over 3 million unique clients a day across 3 servers. | ||
==== What tools/frameworks | ==== What tools/frameworks will we use? ==== | ||
This is an [[Update:Development: | This is an [[Update:Development:Tools|ongoing discussion]] that will hopefully yield the "best tools for the job". | ||
==== What about coding standards? ==== | |||
We are going to stick with the standard Mozilla coding standards where they apply and then [[Update:Development:Best Practices|develop our own]] where they do not. | |||
==== When is X going to happen? ==== | ==== When is X going to happen? ==== | ||
edits