[dev] Recent notification system init changes break rpc access to at least kronolith.

[Michael J Rubinsky]

This commit:
   
https://github.com/horde/horde/commit/cf3fd14107fba9d77ca83171206055cda7383a3a#framework/Core

Breaks accessing kronolith via rpc.php for things like syncing and api  
calls via RPC. I've spent a few hours tracing the code, but I'm  
getting lost in a combination of authentication and notification  
code...what I *do* know is:

During rpc access, the 'horde' application is initialized via  
Horde_Registry::appInit(), this instantiates $registry, during which  
the notification system is initialized. Since we now no longer filter  
out unauthenticated apps, every application with a setupNotification  
method has this method called...which initializes each application.  
This access occurs before the registry is even fully constructed. In  
Kronolith, this leads to other applications' API attempting to be  
called to setup e.g., timeobject calendars.

When the rpc server eventually calls e.g.,  
Horde_Kronolith_Api::export(), the list of kronolith shares is empty.  
I admit I'm not sure why this happens, my first thought was something  
getting lost/corrupt during all the app pushes/pops happening during  
initialization of the 'horde' app.

Reverting this commit restores ActiveSync functionality for me and  
stops draining my Droid's battery in 2 hours.

Anyone have any ideas as to where to look further?
-- 
mike

The Horde Project (www.horde.org)
mrubinsk at horde.org
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 6096 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://lists.horde.org/archives/dev/attachments/20120212/73c0c1c4/attachment.bin>