Merge with main Services project
magico - September 26, 2008 - 13:43
| Project: | AMFPHP |
| Version: | HEAD |
| Component: | Code |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | by design |
Jump to:
Description
I understand that this is a separated project, to minimize the download size of services.module
But this project being totally dependent on services.module, wouldn't it be better to merge all officially (and most used) servers into the main project?
#1
The separation of AMFPHP and Services has nothing to do with download size.
Combining common servers into Services module is something that may be considered in the future, but for now, the separation allows for separate development timelines, which is better for both projects. Services is meant to be an API, any server implementation should be supported and maintained by someone who knows that particular technology, which may become an issue if Services core included and maintained several different server implementations.
That said, please elaborate on why this would be a good idea, as the discussion is still open.
Thanks,
Scott