[#4561] Port DIMP's imp.php services to IMP's API
Summary Port DIMP's imp.php services to IMP's API
Queue IMP
Queue Version Git master
Type Enhancement
State Assigned
Priority 1. Low
Owners Chuck Hagenbuch <chuck (at) horde (dot) org>
Requester Chuck Hagenbuch <chuck (at) horde (dot) org>
Created 10/26/2006 (981 days ago)
Due
Updated 07/02/2009 (yesterday)
Assigned 07/02/2009 (yesterday)
Resolved
Attachments
Milestone IMP 5.0
Patch No

History
07/02/2009 Chuck Hagenbuch Version ⇒ Git master
 
07/02/2009 Chuck Hagenbuch Assigned to Chuck Hagenbuch
State ⇒ Assigned
 
11/09/2008 Chuck Hagenbuch State ⇒ Accepted
 
07/29/2007 Chuck Hagenbuch State ⇒ Stalled
 
11/23/2006 Chuck Hagenbuch Comment #3 Reply to this comment
Yes, because that's how the js code should be making calls.
11/23/2006 Michael Slusarz Comment #2 Reply to this comment
When DIMP (and MIMP for that matter) get folded into IMP, do we really 
gain anything by making API calls within the application?
10/26/2006 Chuck Hagenbuch Comment #1
Summary ⇒ Port DIMP's imp.php services to IMP's API
Type ⇒ Enhancement
Priority ⇒ 1. Low
State ⇒ Accepted
Queue ⇒ IMP		 Reply to this comment
These kinds of things should be in IMP's API, and then used directly 
by DIMP's js calls where possible, and perhaps used by MIMP instead of 
loading IMP libraries.