What is the nature of the data you are transferring?
-Mike
"Michael F.
After doing a longer session (about 20 minutes), I am getting
about 80% in both directions now..
> Doing compression with SSH I am getting about 70% compression
> outbound and 80% compression inbound..
>
> I have not investigated how OpenSSH implements compression on
> the TCP stream though so I
Doing compression with SSH I am getting about 70% compression
outbound and 80% compression inbound..
I have not investigated how OpenSSH implements compression on
the TCP stream though so I am not sure how great of gauge this
is..
> Update. I am finding that you can get better compression ratios
hi folks,
we are three people and would like to contribute some code to the
jabber community. our idea is to establish filesharing over jabber.
we do this for a project in school which will start monday (7.1.2),
from that day on we have only three weeks to get it done.
i talked about our plans
There's an available public storage mechanism which could probably be
adapted for this purpose. Arbitrary XML can be stored within the roster of a
user under a custom namespace , this is publically accessible via an IQ
'get' to the namespace and data element. The implementation is pretty close
to
On Fri, Jan 04, 2002 at 09:38:49AM -0500, Nigel Kerr wrote:
> i've always wanted something i'll loosely call "annotations on the
> web", a means by which i and other users can create annotations for
> different URLs, and be able to share these annotations amongst
> ourselves. there have been a va
Update. I am finding that you can get better compression ratios, up to
around 57%, by maintaining the LZ dictionary between packets. Also this
reduces the processor hit asymptotically (but still quite nonzero) with
more packets sent along.
This technique raises still other problems, though, most
Ignoring computational costs, the biggest technical hurdle will probably be
that, because of compression, the boundary between two XML Packets is not
guaranteed to be the boundary between bytes in the resulting compressed
stream. Messages might not be interpreted until more data arrives, and thus
I tracked the problem down to aimtrans.so ... and
running it in a separate process (see http://www.saint-andre.com/jabber/xml/)
solves the problem. Perhaps jabber.xml allow one to specify that a service gets
its own process, and jabberd would then handle creation of the
extra process(es)...
hi Sebastiaan, hi all,
Quoth "Sebastiaan 'CBAS' Deckers" <[EMAIL PROTECTED]>:
> Hi,
>
> Would that be like a message board that attaches itself to websites?
> (perhaps visualized with a browser plugin)
this could certainly be one usage scenario of the kind of annotations
i'm thinking of, but i
On Sat, 05 Jan 2002 02:55:58 +
"Amarnath Yara" <[EMAIL PROTECTED]> wrote:
> Hi all, I have been trying to install the new icqv7-t on redhat linux 7.2
> and getting the error message "You won't be able to compile the ICQv7-t
> unless you specify the path to jabber source (headers)".
>
> The
Hi Adam, I looked over some of the DotGNU mailing list archives at the
discussion you are referring to.
One person from DotGNU says
---
At the end of the day, it is easier to just gzip it and forget about
the problem. No data loss, and roughly the same level of
compaction. Highly redundant dat
We could use ASN.1 to rewrite the XML markup in a terser format, and
probably we'd do about as well as gzip for much less processing power. This
would do darn well for presence tags which tend to be highly regular. But
ASN.1 wouldn't really help us for arbitrary message or iq payloads which
are h
The RC4 encryption that SSL can (I think usually?) use is much less
processor intensive than compression. I don't know how it compares to
slower algorithms like 3DES or IDEA, but I would not be suprised if RC4 is
several orders of magnitude faster than gzip (LZ77+Huffman). Disregarding
one-time i
Hi all, I have been trying to install the new icqv7-t on redhat linux 7.2
and getting the error message "You won't be able to compile the ICQv7-t
unless you specify the path to jabber source (headers)".
The "README" says that configure demands to provide path to
jabber-1.4.2-test sources but h
15 matches
Mail list logo
