#4966 NORM Future : OLPC activity PEP notification capabilities should be put in separate bundles

[Zarro Boogs per Child]

#4966: OLPC activity PEP notification capabilities should be put in separate
bundles
-------------------------------+--------------------------------------------
  Reporter:  daf               |       Owner:  smcv          
      Type:  defect            |      Status:  new           
  Priority:  normal            |   Milestone:  Future Release
 Component:  telepathy-gabble  |     Version:                
Resolution:                    |    Keywords:                
  Verified:  0                 |  
-------------------------------+--------------------------------------------
Changes (by jg):

  * milestone:  Never Assigned => Future Release


Old description:

> When we have a server component to query about activity properties, we
> won't need to use PEP to get these properties. We should be able to turn
> off the +notify capability for activity properties when we don't need it;
> we can do this by putting it in a separate bundle.
>
> We should also split out the activities and current_activity stuff into a
> different bundle.
>
> We shouldn't have a non-notify URL when we have a +notify URL — it's
> redundant.

New description:

 When we have a server component to query about activity properties, we
 won't need to use PEP to get these properties. We should be able to turn
 off the +notify capability for activity properties when we don't need it;
 we can do this by putting it in a separate bundle.

 We should also split out the activities and current_activity stuff into a
 different bundle.

 We shouldn't have a non-notify URL when we have a +notify URL — it's
 redundant.

--

-- 
Ticket URL: <http://dev.laptop.org/ticket/4966#comment:1>
One Laptop Per Child <http://dev.laptop.org>
OLPC bug tracking system