Re: [AOLSERVER] nsmemcache driver issue with data over 2kb

2010-09-05 Thread Sep Ng
I have run some tests and Majid's changes fixed the bug, so I don't think my patch is relevant anymore. Cheers. On Sep 4, 11:12 am, Sep Ng thejackschm...@gmail.com wrote: Yes sir!  As soon as possible, I will look at it and determine whether it's still relevant.  I'll post a new diff if

Re: [AOLSERVER] nsmemcache driver issue with data over 2kb

2010-09-05 Thread Dossy Shiobara
OK, I didn't see this before I sent my previous message -- great! Thanks for confirming. On 9/5/10 7:00 PM, Sep Ng wrote: I have run some tests and Majid's changes fixed the bug, so I don't think my patch is relevant anymore. Cheers. -- Dossy Shiobara | do...@panoptic.com |

Re: [AOLSERVER] nsmemcache driver issue with data over 2kb

2010-09-03 Thread Dossy Shiobara
After you test the latest code from Majid, determine if your patch is still relevant. If it is, I'll merge it in. On 8/31/10 7:17 PM, Sep Ng wrote: Okay, I guess I'll simply post the diff patch here for anyone who needs it. -- Dossy Shiobara | do...@panoptic.com |

Re: [AOLSERVER] nsmemcache driver issue with data over 2kb

2010-09-03 Thread Sep Ng
Yes sir! As soon as possible, I will look at it and determine whether it's still relevant. I'll post a new diff if needed. On Sep 4, 10:55 am, Dossy Shiobara do...@panoptic.com wrote:  After you test the latest code from Majid, determine if your patch is still relevant.  If it is, I'll merge

Re: [AOLSERVER] nsmemcache driver issue with data over 2kb

2010-08-31 Thread Sep Ng
Okay, I guess I'll simply post the diff patch here for anyone who needs it. --- nsmemcache.c.4.5.1 2010-08-30 06:56:06.0 +0800 +++ nsmemcache.c2010-08-30 11:19:20.0 +0800 @@ -50,6 +50,7 @@ #define MC_SERVER_DELETED 2 /* Server is not used anymore */ int

[AOLSERVER] nsmemcache driver issue with data over 2kb

2010-08-30 Thread Sep Ng
Hi, I've been trying to use nsmemcache and integrate it with aolserver but I noticed that there's this bug where if you retrieve data over 2kb, the data gets truncated. After inspection, it looks like it's because the buffer size allocated when reading the contents via Ns_SockRecv is not