[zeromq-dev] FileMQ Manual Send/Recv + Symbolic Link

[Ho-Gyun Choi]

Pieter,

> Are you replacing an old file with a new one with different size and
> modified date? It should detect that. I'll test it.

Yes, I think so. Shouldn't just opening the file in the server stage
directory after it has already been sent once, and appending lines of new
data into it, saving it and closing it, do the trick?

> Right, symbolic links were meant to handle this. I see that I've
> completely dropped that functionality by mistake, when replacing
> fmq_file with zfile. I'll add that back into zfile.

Thank you. But how am I supposed to request from the server to only send a
particular file or particular set of files, not the whole stage directory.

Is there a way to make it so that the server only sends a particular
file/set of files on a client request instead of a whole directory sync?

Much appreciated,
- HG Choi





Pieter Hintjens <ph <at> imatix.com> writes:

> 
> On Mon, Sep 30, 2013 at 11:24 AM, HG Choi <c.hogyun <at> gmail.com> wrote:
> 
> > I guess bottom line, I want to work around the directory staging in FileMQ.
> > The "Drag and Drop", implementation is very well done and easy to use, but
> > in the edge case where a previously sent file in the send directory is just
> > replaced, not deleted and written over/appended, by a newer edition but with
> > the same file name, the server will not recognize this.
> 
> Are you replacing an old file with a new one with different size and
> modified date? It should detect that. I'll test it.
> 
> > That is why I would like the option of being able to manually send and
> > receive files located in path "/X" by method calls, completely autonomous
> > from the current patch system and I think the mounting system..
> 
> Right, symbolic links were meant to handle this. I see that I've
> completely dropped that functionality by mistake, when replacing
> fmq_file with zfile. I'll add that back into zfile.
> 
> Using symbolic links, you create a link file in a staging directory
> (in the FileMQ tree), and that is then resolved to the full file,
> which is sent and arrives in the same staging directory on clients.
> 
> -Pieter
>