Thanks, Siddhant; I think this version is much improved over the
previous attempt.
Thank *you*! I have revised it again and its waiting for you! :)
I'd probably try not to get into the details of what the session db file
might look like; that's probably one of the things we'd need to
Sorry I forgot to provide the link of my revised proposal, in the reply.
You can see it here - http://docs.google.com/Doc?id=ddkwv4gn_3dgvxf5c6
Regards,
Siddhant
Hi.
I guess my concepts were twisted. I have made a new proposal, incorporating
what all you have suggested me, and what all I have been able to grasp.
I have proposed my solution here -
http://siddhantgoel.googlepages.com/gsoc_gnu.pdf .
Please tell me if this one is fine, or if something needs to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Siddhant Goel wrote:
Hi.
I guess my concepts were twisted. I have made a new proposal,
incorporating what all you have suggested me, and what all I have been
able to grasp.
I have proposed my solution here -
Hi!
Thanks for such a detailed explanation of the task involved. It surely did
help in creating a solid base. I have already started working on it.
I have also prepared the following proposal for GSoC -
http://siddhantgoel.googlepages.com/gsoc_gnu.pdf
It would be great if you could check it and
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Siddhant Goel wrote:
Hi!
Thanks for such a detailed explanation of the task involved. It surely
did help in creating a solid base. I have already started working on it.
I have also prepared the following proposal for GSoC -
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Charles wrote:
On Fri, Mar 21, 2008 at 2:33 AM, Micah Cowan [EMAIL PROTECTED] wrote:
The intent is that all the writer operations would take virtually no
time at all. The sidb_read function should take at most O(N log N) time
on the size of the
On Sat, Mar 22, 2008 at 12:14 AM, Micah Cowan [EMAIL PROTECTED] wrote:
YAML uses UTF-8; I'm beginning to think YAML may not be what we want,
though, given that the definition for a given entry may be interposed
with defining content for other entries; I don't want to kludge that by
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
(I've rearranged your post slightly so that the answers are ordered more
conveniently for me.)
Siddhant Goel wrote:
Hi.
I couldn't gather much from the wget source code; so want to put up some
questions.
1. Does this necessarily have to be a
On Fri, Mar 21, 2008 at 2:33 AM, Micah Cowan [EMAIL PROTECTED] wrote:
The intent is that all the writer operations would take virtually no
time at all. The sidb_read function should take at most O(N log N) time
on the size of the SIDB file, and should take less than a second under
normal
10 matches
Mail list logo
