headers
Norman Rasmussen | 1 Nov 19:18
Picon
Favicon
Gravatar

Re: [ANN]VTD-XML 2.2

On Oct 26, 2007 8:11 PM, jimmy Zhang <crackeur <at> comcast.net> wrote:
> It is certainly related as VTd-XML is an enabling technology  for XML on
> which
> XMPP is based...
> my real questioN: isn't it obvious?

Not really, as far as I understand XMPP is generally associated with
the exchange of vastly many XML elements within a single document. Now
I know that the VTD docs say that the XML document is updatable, but
as far as XMPP is concerned, once a node is parsed and processed, you
can forget about it's data entirely.  It seems that VTD is a 'bounded'
solution, i.e. there's no scope for throwing data away once it has
been processed.  I'm not sure if XMPP streams on busy servers could
reach the 30bit/1gb limit imposed by the VTD format, but it seems that
VTD is better oriented to parsing disk based files, rather than
streams.

I applaud you on promoting the parser, too many xmpp projects go and
re-write an XML parser.  I guess this has mostly been because of lack
of decent XML parsers being available at the time of writing, but even
projects like agsXMPP and XMPP.NET do it  (just to name two examples).
 I'm also not sure to what degree XMPP has glitches that
'framework/off-the-shelf' XML parsers can't handle, and therefore some
projects probably end up fairly far down the road with a standard
parser, before having to backtrack, and implement their own parser to
work around some tiny niggly bug.

--

-- 
- Norman Rasmussen
 - Email: norman <at> rasmussen.co.za
(Continue reading)

Permalink | Reply | 0 comments |
headers
Ernest Nova | 1 Nov 21:43
Picon
Favicon

Google to Connect to Other IM Networks Using Jabber Transports?


FWIW:

http://googlesystem.blogspot.com/2007/10/google-to-connect-to-other-im-networks.html

or http://tinyurl.com/2p9hh3
Permalink | Reply | 12 comments |
headers
Peter Saint-Andre | 1 Nov 22:00
Favicon

Re: Google to Connect to Other IM Networks Using Jabber Transports?

Ernest Nova wrote:
> FWIW:
> 
> http://googlesystem.blogspot.com/2007/10/google-to-connect-to-other-im-networks.html

Yes I saw that in my RSS feeds this morning. I don't have any inside
information to share about it, but it's intriguing. However, it seems to
me that they would prefer to do native XMPP with other services since
that would give them real federation (not the client-proxy hack involved
in traditional transports).

Peter

--

-- 
Peter Saint-Andre
https://stpeter.im/
Attachment (smime.p7s): application/x-pkcs7-signature, 7338 bytes
Permalink | Reply | 6 comments |
headers
Tomasz Sterna | 1 Nov 22:12
Favicon
Gravatar

Re: Google to Connect to Other IM Networks Using Jabber Transports?

Dnia 01-11-2007, Cz o godzinie 15:00 -0600, Peter Saint-Andre pisze:
> >
> http://googlesystem.blogspot.com/2007/10/google-to-connect-to-other-im-networks.html
> 
> Yes I saw that in my RSS feeds this morning. I don't have any inside
> information to share about it, but it's intriguing.

The code shown is a list of methods to use for transport of AJAX request
made by the client to the server. (browser native, or emulated with
IFrames)
It has nothing to do with Jabber Transports.

--

-- 
  /\_./o__ Tomasz Sterna
 (/^/(_^^'  Xiaoka.com
._.(_.)_  XMPP: smoku <at> xiaoka.com
Permalink | Reply | 1 comment |
headers
Nicolas Vérité | 1 Nov 22:17
Picon
Gravatar

Re: Google to Connect to Other IM Networks Using Jabber Transports?

On 11/1/07, Tomasz Sterna <tomek <at> xiaoka.com> wrote:
> Dnia 01-11-2007, Cz o godzinie 15:00 -0600, Peter Saint-Andre pisze:
> > http://googlesystem.blogspot.com/2007/10/google-to-connect-to-other-im-networks.html
> >
> > Yes I saw that in my RSS feeds this morning. I don't have any inside
> > information to share about it, but it's intriguing.
>
> The code shown is a list of methods to use for transport of AJAX request
> made by the client to the server. (browser native, or emulated with
> IFrames)
> It has nothing to do with Jabber Transports.

Besides, the IM fields that you will be able to fill in for a contact,
are already present.

Nÿco
--

-- 
Nicolas Vérité (Nÿco) mailto:nicolas.verite <at> gmail.com
Jabber ID : xmpp:nyco <at> jabber.fr
http://linuxfr.org/ - http://fr.wikipedia.org/ - http://www.jabberfr.org/
Permalink | Reply | 0 comments |
headers
Peter Saint-Andre | 2 Nov 19:19
Favicon

http://www.jabber.org/crossdomain.xml for Flash

Currently in the document root for http://www.jabber.org/ we have a file
called "crossdomain.xml".

This is/was used by Flash clients to connect to the jabber.org XMPP
service. However, I don't know if it is still in use. If your
application depends on this, please let me know. Otherwise it may
disappear during the impending upgrade of www.jabber.org to Drupal.

Thanks!

Peter

--

-- 
Peter Saint-Andre
https://stpeter.im/
Attachment (smime.p7s): application/x-pkcs7-signature, 7338 bytes
Permalink | Reply | 2 comments |
headers
Raffaele Sena | 3 Nov 04:38

http://www.jabber.org/crossdomain.xml for Flash

Flash still checks the crossdomain file for "applications" hosted on one 
site that are making network request to a different site, so if you want 
to support Flash XMPP clients accessing jabber.org you should keep 
hosting the file.

thanks!

-- Raffaele

Peter Saint-Andre wrote:
> Currently in the document root for http://www.jabber.org/ we have a file
> called "crossdomain.xml".
> 
> This is/was used by Flash clients to connect to the jabber.org XMPP
> service. However, I don't know if it is still in use. If your
> application depends on this, please let me know. Otherwise it may
> disappear during the impending upgrade of www.jabber.org to Drupal.
> 
> Thanks!
> 
> Peter
>
Permalink | Reply | 1 comment |
headers
Andre-John Mas | 5 Nov 15:46
Picon
Favicon

Re: Google to Connect to Other IM Networks Using Jabber Transports?


On 1-Nov-07, at 17:00 , Peter Saint-Andre wrote:

> Ernest Nova wrote:
>> FWIW:
>>
>> http://googlesystem.blogspot.com/2007/10/google-to-connect-to-other-im-networks.html
>
> Yes I saw that in my RSS feeds this morning. I don't have any inside
> information to share about it, but it's intriguing. However, it  
> seems to
> me that they would prefer to do native XMPP with other services since
> that would give them real federation (not the client-proxy hack  
> involved
> in traditional transports).

Yup, from my experience few clients make the use of transports clear and
easy to understand. By ensuring everything is happening on the server  
side
it makes things easier for the average user.

The only thing, is I am not sure I can imagine how they would deal  
with MSN,
which allows for accounts with domain names which aren't in the  
msn.com or
hotmail.com realm. Maybe this could be a fallback method if everything  
else
fails, something like:
    - if matches @yahoo.* try connecting using Yahoo
    - if matches @icq.com try connecting using icq
(Continue reading)

Permalink | Reply | 3 comments |
headers
Norman Rasmussen | 5 Nov 15:53
Picon
Favicon
Gravatar

Re: Google to Connect to Other IM Networks Using Jabber Transports?

On Nov 5, 2007 4:46 PM, Andre-John Mas <ajmas <at> sympatico.ca> wrote:
> The only thing, is I am not sure I can imagine how they would deal
> with MSN, which allows for accounts with domain names which aren't in the
> msn.com or hotmail.com realm.

Maybe force the xmpp domain for all msn contacts to be msn.com and
then users would have a jid of: joebloggs%hotmail.com <at> msn.com (yugh,
depricated!) or joebloggs\40hotmail <at> msn.com if you're using jid
escaping properly.

--

-- 
- Norman Rasmussen
 - Email: norman <at> rasmussen.co.za
 - Home page: http://norman.rasmussen.co.za/
Permalink | Reply | 0 comments |
headers
Peter Saint-Andre | 5 Nov 18:05
Favicon

Re: Google to Connect to Other IM Networks Using Jabber Transports?

Andre-John Mas wrote:
> 
> On 1-Nov-07, at 17:00 , Peter Saint-Andre wrote:
> 
>> Ernest Nova wrote:
>>> FWIW:
>>>
>>> http://googlesystem.blogspot.com/2007/10/google-to-connect-to-other-im-networks.html
>>>
>>
>> Yes I saw that in my RSS feeds this morning. I don't have any inside
>> information to share about it, but it's intriguing. However, it seems to
>> me that they would prefer to do native XMPP with other services since
>> that would give them real federation (not the client-proxy hack involved
>> in traditional transports).
> 
> Yup, from my experience few clients make the use of transports clear and
> easy to understand. By ensuring everything is happening on the server side
> it makes things easier for the average user.
> 
> The only thing, is I am not sure I can imagine how they would deal with
> MSN,
> which allows for accounts with domain names which aren't in the msn.com or
> hotmail.com realm. Maybe this could be a fallback method if everything else
> fails, something like:
>    - if matches @yahoo.* try connecting using Yahoo
>    - if matches @icq.com try connecting using icq
>    - if matches @gmail.com try connecting using Jabber
>    - try other smart matches
>    - else attempt Jabber and on failure try MSN
(Continue reading)

Permalink | Reply | 0 comments |

Gmane