Obviously, there is not one single solution that would satisfy all needs; architecture is always a compromise. I want to create a framework initially aimed at RAD web games. The target language is PHP, although the architecture should be widely applicable.
The goals that I have in mind for this structure are: flexibility in how to achieve the result; maximum comfort for developers; connection modules such as LEGO® Blocks many types of input, many types of output, one format for processing.
Goals that are not a priority are speed, enterprise use and making money. It should be an open source project.
The cornerstone of this design is that all content is processed to XML before conversion (the idea is based on the EAI system I worked with, eGate). The level of data abstraction - I hope some clever ORM - is not important now. The result will be generated using XSLT or any other custom modules, for almost any client - HTML for older browsers, XHTML / HTML5 for modern browsers, simple HTML for mobile clients, XML for AJAX / XMLRPC, etc.
The main reasons for using XML:
- this is a famous standard
- existing tools like XPath, SimpleXML, and the DOM for navigating and modifying content
- XSLT provides a powerful and unified way to convert code to any soup soup.
- I believe that XML markup is very easy to read, so I don't think the benefits of JSON or YAML matter here.
- , , XSLT
:
- : , GPCS, [XML]
- /: -, XML (, , , )
- : -, . , , , ..
- : XML ( , XSLT), .
(, , , , , ), .
, : , ? , / , ? ?