30 lines
1.4 KiB
Plaintext
30 lines
1.4 KiB
Plaintext
|
|
||
|
As at 2010.01.03
|
||
|
|
||
|
Features still to be implemented
|
||
|
* More testing of the outbound socket client template code
|
||
|
* Implement Send event command
|
||
|
* Testing of SendMsg command
|
||
|
* Refactor the api of the inbound client into the abstract handler so it is also available in outbound handlers as well
|
||
|
* Per event(s) listener
|
||
|
* Provide XML event handling - not sure if this is useful since the raw event is not exposed, although it could be if needed.
|
||
|
* Implement 'myevent' event subscription for inbound - not a priority here, easy if required.
|
||
|
* Provide timeout protection on the client.sendSyncApiCommand(). It will currently block for ever if get no response from server.
|
||
|
* Working examples in an example project (started).
|
||
|
* Add OSGi example
|
||
|
* Chase down the apparent issue with Netty when using executor in pipeline (wierd).
|
||
|
|
||
|
Distribution
|
||
|
* Basic usage docs
|
||
|
* Package jar, javadocs, source and dependencies (slf4j, netty) for people to trial without having to build.
|
||
|
* Find out how (if ok) to put binary distribution on files.freeswitch.org
|
||
|
* Cut a release, look at usage of tags in FS svn repo.
|
||
|
|
||
|
Quality items
|
||
|
* Ask FS dev team for any ESL event generation test strategies/suites.
|
||
|
* Are all message header names in the enum ?
|
||
|
* Improve Javadoc coverage
|
||
|
* Add cross references to the FS wiki in the Javadocs .. eg list of api commands and events.
|
||
|
* Add unit test coverage
|
||
|
* Investigate availability of FS JIRA for issue tracking
|