On Tue, 20 Nov 2001, Will Glynn wrote:
> I've been working on CFCP, a C++ class library for FCP communication. I've
> released version 0.1 which, though unpolished, works.
>
not bad. If there's any annoying protocol issues, I'm the person to
bother with them, especially in regards to the metadata spec.
> Structure is as follows:
> CFCP - engine object that keeps tabs on sockets, threads, and other
> housekeeping information
> ::Hello - sends a Hello message and interprets the repsonse
> ::GenerateSVK - sends a GenerateSVKPair message and interprets the
> response
> ::ClientGet - ...
> [other message classes]
> ::Request - handles metadata, follows redirects, etc.
> ::Insert - does a "smart insert" (picks proper key type) and handles
> metadata generation
> ::Socket - handles sockets; platform-specific
> ::Thread - handles threading; platform-specific
>
I'd like to know how you handle metadata with redirects. I.e. you can
have a redirect that has metadata on it (about the document it's
redirecting you to) and also have a document with metadata. What do you
return as metadata?
> There's also a couple other utility classes, but that's about it.
>
> Sample code:
>
> CFCP engine;
> CFCP::Request obj(&engine);
> obj.SetKey("SSK at gpOQ5OUAgJiCferl1DD2n5kMzw4PAgM/delta407//");
> obj.SetFilename("c:\index.html");
> if (obj.DoExchange() == 0)
> {
> // success
> }
> else
> {
> // failure
> }
>
Looks pretty easy, although is this an insert or a request?
Thelema
--
E-mail: thelema314 at bigfoot.com If you love something, set it free.
GPG 1536g/B9C5D1F7 fpr:075A A3F7 F70B 1397 345D A67E 70AA 820B A806 F95D
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 232 bytes
Desc: not available
URL:
<https://emu.freenetproject.org/pipermail/devl/attachments/20011121/980ccf0e/attachment.pgp>
