-
Notifications
You must be signed in to change notification settings - Fork 1
/
Copy pathTODO.txt
61 lines (54 loc) · 2.37 KB
/
TODO.txt
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
51
52
53
54
55
56
57
58
59
60
61
$Id: TODO.txt,v 1.5.2.2 2010/05/12 15:38:42 pounard Exp $
Yamm todo list
==============
Latest stuff (important)
------------------------
* Create a view filter which says "update is more recent than last uuid". This
will allow incremental updates. Dependency fetching should also be capable of
returning such message as "entity has not been updated" instead of sending
pragmatically all dependencies.
* Handle properly object deletion on client side (clean uuid). This means more
Drupal hooks implementation for common types.
* Client should check for DNS/server base url matching when receiving an order
to avoid security issues or DDoS attacks.
* When pushing to a client, allow site admin to select profile.
* Allow admin to select a default profile per client.
* Content copy should not be required, and node export should fail if type is
unknown and content copy is disabled.
* Client error reporting should be more precise, and should give back erroneous
entity uuid to server, plus a message or an error code.
* Implement a view display plugin in order to ensure our views are meant to be
used with profiles.
* Finish views sharing (should be a fun feature!).
* If server is configured to change users password, and send the configured
client user password, it should also update its own configuration to be able
to send it data later.
* Use XoXo objects for clients.
* Use OOX registry for entities.
Done
----
* Add last update time into yamm_uuid table.
* Change "server" configuration option in client by "allowed servers" with a
list or one or more server.
* Add the server url in client transaction table.
* Server should send its own base url as a parameter when pushing the order to
client so the client would now on which server it should fetch data.
* Server profile handling should be rewrote in order to match new naming
conventions.
Client handling
---------------
* Add profile select box into client overview page for pulling
* Implement reporting on jobs (number of object saved/updated)
All
---
* Implement hook_requirements() for tricky part configuration checks
- Check server has (default) profile
- Check server has client(s)
- Check client has server
Server
------
* Spec and implement a scheduler using hook_cron()
Cron
----
* For server, purge old transactions
* For client, check jobs has timeouted, and clean them