1 * Write up more tests in /t/
6 * Automate configuration when installing (PIN-code, port etc ...)
7 * Automate the test in /t/ also in function of choosing the config parameters
8 * Clean up and refine the logging. COnsolidate this in one logfile for the
11 - Log::Agent: Need to investigate
13 * Try to investigate the possibility to build in a QUEUE ( cache?)
15 - Transport Spool would be mandatory ( super class transport )
16 - Use Cache::File ??? -> probably Cache::Cache!
17 - When system crashes, should be able to pick them up
19 * MCube support and Clickatel support
20 * Delivery report support (message status)
21 - How to give a message an ID (possible link to caching here)
22 - How to communicate the message ID back? Probably need to
23 change NBS.pm interface, because a message ID must be brought back
24 - Probably Message.pm class that has a ->body, ->status method?
25 - SMS-SUBMIT-REPORT, SMS-DELIVER-REPORT PDU types
26 !! OBJECTIFY PDU.pm !!
28 * Refactor Transport.pm -> error message needs to be included in which
30 - Look at cache and ID ... integrate closer!
32 * EMS ( Enhanced Message System )