generic/interaction session initiation

[MarkSwanson]

Hello,

What a potentially fascinating project!
I have a simple test application based on the mapsync demo.
I'm receiving messages, but only when an interaction session is
created. This isn't useful to me because the test application isn't
able to establish the interaction session on its own - the user has to
do mouse clicks to enable this.

What I need:
1. Browser starts up, sameplace logs in to a jabber server. Works!

2. HTML/JavaScript application starts up, establishes an interaction
session on its own. Impossible???
The interaction session is with a server - not a real person.

The reason why I want this is so that the HTML/JavaScript client
application can just sit idle waiting for events to be pushed from a
server.

This seems to be an excellent solution to the polling problem, but I
can't expect my users to remember to do the mouse clicks to establish
the interaction session.

I see that connectPanel() MUST be called. Perhaps a scriptlet could do
this for specific incoming messages?
It would have to walk all open tabs, find ... nevermind, that's just
unworkable...and I'm guessing this is the show stopper reason why this
just isn't going to be difficult.

In a nutshell I think this is required:
sameplace must hook in to every open tab during the tabs onload() and
scan for the divs (sameplace-incoming, sameplace-outgoing), and link
in a samplace communications channel (DOM event callback functions)
that the tab javascript can use to establish an xmpp interaction
session.
The interaction session would use divs xmpp-incoming and xmpp-
outgoing.

Of course, I just stumbled upon sameplace and you may already have a
solution for this :-)
If not, any interest in solving this problem? This solution could end
client side polling for good. At least in Firefox :-)

[Massimiliano Mirra]

Hi Mark,

sorry for the late reply. Future plan is to allow pages to specify,
either in the body as microformat or in the head as a
meta/link/something else tag, a default interaction contact.
SamePlace would see that and ask the user permission to connect the
page to the specified contact, with the usual options "allow once",
"allow always", "deny". A user confirmation is needed at least once
for obvious security reasons.

There's no roadmap for this at the moment, although if you need it to
implement something interesting, that surely helps increasing the
priority. :)

-m