only one task and it will never execute the first task
anyway.
Paul
%xmlrpc-asyncfix.diff
Description: application/applefile
xmlrpc-asyncfix.diff
Description: Binary data
%xmlrpc-anyport.diff
Description: application/applefile
xmlrpc-anyport.diff
Description: Binary data
--
Philosophie de baig
o add this patch to the Bugzilla database, but
although I can access bug reports for the XML-RPC product, e.g.:
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=28982
Clicking new doesn't allow me to pick this product. I'm a little bit
confused here.
Paul
%xmlrpc.diff
Description: a
package org.apache.xmlrpc;
/*
* The Apache Software License, Version 1.1
*
*
* Copyright (c) 2001 The Apache Software Foundation. All rights
* reserved.
*
* Redistribution and use in source and binary forms, with or without
* modification, are permitted provided that the followi
, new collections are not
synchronized, which is a bit more efficient.
Would the group be interested in this code?
I'm only interested in server-side (I have a PHP
client), but I can also change the client classes.
Thanks,
Paul
PS Great code set!
I sent an email to rpc-dev earlier today about this problem without noticing
this discussion. What is that status of this patch? I don't see it
represented in the CVS tree.
- Original Message -
From: "Daniel Rall" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, February 13,
py to provide a patch, if someone would kindly let me know how
to make a patch.
If I'm mistaken, and this functionality already exists, please let me know!
Thanks,
Paul Oehler
his one should let the character go (p. 25):
if (sixBit == 66) byteShift--;
Cheers,
Paul
orrect yardstick
for a cross-system base64 implementation), you'll see that this isn't quite
the correct behavior. Among other things, whitespace and illegal characters
are to be ignored.
RFC 2045, S6.8:
http://www.ietf.org/rfc/rfc2045.txt
-- Paul
