forked from klnusbaum/UDJ-Server
-
Notifications
You must be signed in to change notification settings - Fork 1
/
Copy pathTODO
52 lines (45 loc) · 2.33 KB
/
TODO
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
HOST CLIENT
- Enable seemless playback by queuing up songs that are about to be played.
And what's more, songs should fade into one another. Like a real dj would.
Sync the beat of the new song to the beat of the the one that is currently
playing, fade into new song, then gradual return beat of new song to normal.
- Import iTunes library capability
- Need to be able to handle the current song being changed from another client.
- Need to be able to handle the event being ended from another client.
* If a song is removed from the library mid event, need to make sure that
the available music, active playlist, and anything else that references the
library table is updated accordingly
* current syncing model always assumes that a library entry or available
music entry is successfully and completely added with the server before any
potential delete operations is started. need to enforce this work flow some
how. For instance, don't even allow a syncstatus to change unless it's set to
isSynched. Should be a simple trigger on the database.
* make the enable/disable of the playback widget more reasonable.
* Handle multiple users on the same machine
* When getting a 404 on deleting a song, the host client should just
go ahead and mark the song as sycned and deleted because
clearly the server didn't even know about it in the first.
* Fix time added so it actually looks decent
* Available Songs to come back when the client is quit in the middle
of an event.
- password protected events
ANDROID APP
- Parties with passwords
- Switch auth dialog to dialog fragment
- Handle when credentials change
- password protected events
SERVER
-Maybe If two users add the same song within a certain threshold of oneanother (e.g.
the same song was added by two different users within 10 seconds of one another)
just merge the song requests
-Test exception cases.
-Test for commands that are being issued to a party that is over.
* Implement passwords
-Need to do json validation. Make sure it's good json and make sure it looks
like its supposed to (i.e. doesn't have certain attributes missing)
*Validate that the libid's that are being requested to be added to the
active playlist to make sure that they are in the list of available songs.
OVERALL
-Rdio and Spotify integration!!!!!!
-Client spec list (minimum fucntionality for each client, along with optional
functionality).