| 1 |
$Id: TODO,v 1.4 2001/03/22 21:38:51 archon Exp $ |
| 2 |
|
| 3 |
=head1 TODO |
| 4 |
|
| 5 |
=over 4 |
| 6 |
|
| 7 |
=item _send_mode () |
| 8 |
|
| 9 |
Should we throw an error if $response is not success? carp? |
| 10 |
|
| 11 |
=item lastupdate () |
| 12 |
|
| 13 |
Should this be encapsulated? |
| 14 |
|
| 15 |
=item lastsync () |
| 16 |
|
| 17 |
Should this be encapsulated? |
| 18 |
|
| 19 |
=item is_success() |
| 20 |
|
| 21 |
Return if an operation was successful. Useful? |
| 22 |
|
| 23 |
=item Front ends to Journal::get and Journal::post |
| 24 |
|
| 25 |
Do we need these? |
| 26 |
|
| 27 |
=item Multi-user support |
| 28 |
|
| 29 |
Right now, we only support one user at a time. When the base class is |
| 30 |
instantiated, the login and password are stored and accessable for the |
| 31 |
subclasses. In order to change users, we have to reinstantiate each of the |
| 32 |
classes. |
| 33 |
|
| 34 |
The alternative is to pass the login/password data each time any of the |
| 35 |
class objects are instantiated. |
| 36 |
|
| 37 |
=item Documentation |
| 38 |
|
| 39 |
Could probably use some more organization |
| 40 |
|
| 41 |
=item LiveJournal::Database |
| 42 |
|
| 43 |
a class that supports storing/retrieving information from various formats |
| 44 |
|
| 45 |
=back |
| 46 |
|
| 47 |
=cut |