Some guidance for multiple widgets... / connections

[willwill]

Hi there,

I'm in the process of completing a widget built with the Collecta API.
In the process of finalizing the prototype I need to make it fit our
application architecture. Our UI basically consists of multiple
dashboards which each contain multiple widgets. I would like to be
able to support multiple Collecta widgets, each with their own search
query/subscription.

Here's where my questions come in: Would it be better to use one
connection with multiple subscriptions or multiple connections/one
subscription each, to make this work? What are the advantages of
either approach? Is anyone aware of timing problems or contention
issues that might arise on either side?

Thanx, any help would be appreciated.

Will

[Dandee Fleming]

Will,

We are about to release something that I think will solve all your
issues. Can you hang tight until tomorrow? Or do you need this right
away for something?

Dandee

[willwill]

Since it's almost midnight in my time zone, tomorrow is just fine.
I'll look forward to whatever you have up your sleeve. :)

Will

[Kronos verela]

Hello my name is kronos and I received this message from you concerning an API and was wondering if this was a deliberate email...If not how did it get filtered to me?

With warm regards 

Yves Kronos Verela

[willwill]

Dandee,

I did enjoy seeing the new widget builder and I have already
integrated your new widget into our social search dashboards.
Unfortunately, that still doesn't answer any of the questions I raised
in the original post, since I'm building new widgets with your API.

So, I'll rephrase: Imagine a dashboard with several widgets, all using
your API. Is it feasible to have several subscriptions running
concurrently over one XMPP connection? Or should I create several
connections each with their own subscription? Does anyone else in your
development team have an opinion on this?

Btw, you would give developers a great head start by sharing the
source code for the widget. Unfortunately you minimize it, so it's
unreadable. I started out with the code from obama.collecta.com and
have managed to understand most of how your model works. What isn't
clear are things like the list of content sources you currently
support, or the formats that returned items have. Somewhere I read
that these are derived from the specs for RSS/Atom?

Any details would help move my work forward faster.

Cheers,
William

On Jan 25, 10:51 pm, Dandee Fleming <thedan...@gmail.com> wrote:

[Christopher Zorn]

Hey William.  I will try and take a stab at your questions.

On Thu, Jan 28, 2010 at 5:59 AM, willwill <wi...@glookr.com> wrote:

Dandee,

I did enjoy seeing the new widget builder and I have already
integrated your new widget into our social search dashboards.
Unfortunately, that still doesn't answer any of the questions I raised
in the original post, since I'm building new widgets with your API.

So, I'll rephrase: Imagine a dashboard with several widgets, all using
your API. Is it feasible to have several subscriptions running
concurrently over one XMPP connection? Or should I create several
connections each with their own subscription? Does anyone else in your
development team have an opinion on this?

It seems best to use one connection here. You can have multiple subscriptions with one account and once connection.

Best practice is have a connection per 'page' or application when using a BOSH connection. If its a straight XMPP connection then the application should use one connection.

 

Btw, you would give developers a great head start by sharing the
source code for the widget. Unfortunately you minimize it, so it's
unreadable. I started out with the code from obama.collecta.com and
have managed to understand most of how your model works. What isn't
clear are things like the list of content sources you currently
support, or the formats that returned items have. Somewhere I read
that these are derived from the specs for RSS/Atom?

I believe there will be some examples soon. The best bet is to find XMPP Pubsub examples and then add the extra subscription options that collecta supports. Maybe someone can post a javascript example here.

The following url has some examples :

http://github.com/metajack/profxmpp

 

Any details would help move my work forward faster.

I hope this helps.
 

[willwill]

Thanks for the insight. It confirmed my assumptions about one
connectionManager per page with multiple views that have subscriptions
and consume content.
I'm well aware of Jack's book. I'll be looking forward to any
additional examples you guys out there put up.

On Jan 28, 3:37 pm, Christopher Zorn <christop...@gmail.com>
wrote:

[Jack Moffitt]

> So, I'll rephrase: Imagine a dashboard with several widgets, all using
> your API. Is it feasible to have several subscriptions running
> concurrently over one XMPP connection? Or should I create several
> connections each with their own subscription? Does anyone else in your
> development team have an opinion on this?

Just to clarify what Christopher already said, the Collecta web site
does a subscription per saved search over a single XMPP connection. So
the system is designed to run this way.

One current bug is that unsubscribing from a single Collecta search
will unsubscribe from them all. We will fix this in the future. For
now you just have to remember to resubscribe in that case.

jack.