Summary | kronolith/lib/api.php missing function in wsdl |
Queue | Kronolith |
Queue Version | 2.3.1 |
Type | Enhancement |
State | Resolved |
Priority | 2. Medium |
Owners | jan (at) horde (dot) org |
Requester | rpolli (at) babel (dot) it |
Created | 05/14/2009 (5886 days ago) |
Due | |
Updated | 01/13/2010 (5642 days ago) |
Assigned | |
Resolved | 06/16/2009 (5853 days ago) |
Milestone | |
Patch | Yes |
Propagate the 'modified' API method (
Request #8274).http://git.horde.org/diff.php/kronolith/docs/CHANGES?rt=horde-git&r1=d9291a87caf42bbf85bb0ff7767934e4bce1003f&r2=24813c63d8759acf39e2f4789512f595c699c3df
http://git.horde.org/diff.php/kronolith/lib/api.php?rt=horde-git&r1=ebdfffb4b98e9be51d55c8a400d29247c3ed10b7&r2=24813c63d8759acf39e2f4789512f595c699c3df
Assigned to Jan Schneider
State ⇒ Resolved
http://cvs.horde.org/diff.php/kronolith/docs/CHANGES?rt=horde&r1=1.165.2.262&r2=1.165.2.263&ty=u
http://cvs.horde.org/diff.php/kronolith/lib/api.php?rt=horde&r1=1.126.2.61&r2=1.126.2.62&ty=u
you want to announce changes and additions in separate SyncML messages.
a "strategy" of managing items. then funambol converts your strategy
in syncml adapting all the communication to the client capabilities
with a series of parachutes for misbehaving clients.
what is done is:
* create a map <uid, timestamp> of all items stored on horde
* then manage this map to retrieve new,updated,deleted items.
anyway:
* being this function implemented, I see no reason not to expose it:
it's definitely useful ;)
* I'll be glad to discuss those stuff with you by mail...maybe the
buglist is not the best place...
http://dev.horde.org/api/kronolith/Kronolith/_lib---api.php.html and
I think should be exposed here and in other modules.
automatically. That's not a reason to expose this method though.
a single call, no matter whether the item were added or modified.
as of now I have to invoke twice getActionTimestamp:
- first with modify
- then with add
you want to announce changes and additions in separate SyncML messages.
http://dev.horde.org/api/kronolith/Kronolith/_lib---api.php.html and I
think should be exposed here and in other modules.
imho retrieving the modify timestamp of one item should be done with a
single call, no matter whether the item were added or modified.
as of now I have to invoke twice getActionTimestamp:
- first with modify
- then with add
Imagine in a tree I got 20% new items, it's 20% more calls...
State ⇒ Feedback
Milestone ⇒
Priority ⇒ 2. Medium
Type ⇒ Enhancement
Summary ⇒ kronolith/lib/api.php missing function in wsdl
Queue ⇒ Kronolith
Milestone ⇒ 2.3.1
Patch ⇒ Yes
State ⇒ New
by webservice
@line 81
+ $_services['modified'] = array(
+ 'args' => array('uid' => 'string'),
+ 'type' => 'int',
+);
@230
+function _kronolith_modified($uid)
+{
+ return __kronolith_modified($uid);
+}