Catalyst-Engine-XMPP2
view release on metacpan or search on metacpan
You have to keep in mind that the resources will be pre-advertised,
and that for each public path action, you will have a public jabber
id, and, at least by now, a separated connection to the server, so
it's probably a good idea to do a carefull planning of which actions
to make public.
Content-Type
XMPP has no support for MIME types. Every message is, by definition,
a XML document. So every request will have the "application/xml"
MIME type. If the response content-type is also "application/xml",
it will be written as raw into the XMPP stream. This will allow SOAP
responses, for instance, to be sent as in XEP-0072.
On the other hand, if the content type is of some other type, it
will be sent as literal string inside a <body> tag, as described by
XMPP RFC3921, this way, interaction with regular IM clients should
be natural.
Scalability
At this point, this engine is single-threaded, which means that it
lib/Catalyst/Engine/XMPP2.pm view on Meta::CPAN
You have to keep in mind that the resources will be pre-advertised,
and that for each public path action, you will have a public jabber
id, and, at least by now, a separated connection to the server, so
it's probably a good idea to do a carefull planning of which actions
to make public.
=item Content-Type
XMPP has no support for MIME types. Every message is, by definition, a
XML document. So every request will have the "application/xml" MIME
type. If the response content-type is also "application/xml", it will
be written as raw into the XMPP stream. This will allow SOAP
responses, for instance, to be sent as in XEP-0072.
On the other hand, if the content type is of some other type, it will
be sent as literal string inside a <body> tag, as described by XMPP
RFC3921, this way, interaction with regular IM clients should be
natural.
=item Scalability
( run in 1.685 second using v1.01-cache-2.11-cpan-524268b4103 )