I am interested in precisely the same concept. My best guess is that it appears that an agent is the equivalent of an embedded robot, meaning, to me, that it doesn't have to suffer any issues of network connection to be engaged as would be a robot. This suggests that an agent is an appropriate approach to federating frameworks perhaps by way of some communication link between the wave federation and the collaboration framework. My collab framework is just now getting off the ground at http://code.google.com/p/bloomer/
Cheers Jack On Wed, Jan 6, 2010 at 7:37 AM, Bernardo Ferreira <[email protected]> wrote: > Hi, > > I'm trying to integrate Google Wave into an existing collaboration > framework. For that purpose, i was planning on using the fedone > reference server and build a robot that would act as a bridge between > Wave and the existing framework. The problem is that the current > version of fedone does not yet contain the robot API. Nevertheless, it > contains the Agent API. > > My question is the following: how reliable is the current > implementation of the Agent API on fedone? should it be used for this > purpose? is Google planning on adding the robot API to fedone (and if > so, when) ? > > Any other comment regarding how I should approach this problem is also > welcome :) > > Thanks in advance, > Bernardo. > > -- > You received this message because you are subscribed to the Google Groups > "Wave Protocol" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/wave-protocol?hl=en. > > > >
-- You received this message because you are subscribed to the Google Groups "Wave Protocol" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/wave-protocol?hl=en.
