IPC in Everything 1.4

[void]

The Everything IPC now exposes the entire Everything DB API.

The SDK will be updated soon to include examples.

The updated IPC header is available in the SDK now:
http://www.voidtools.com/support/everything/sdk/ipc/

[Link]

FYI: This move makes it seem that you are not going to release the whole source code.

Also why are you using your own string length function rather than the standard one?

[Gisle Vanem]

It would be nice to have an IPC message to get information on the bitness of EveryThing. I.e. if it is a 32-bit or 64-bit version.

[void]

It would be nice to have an IPC message to get information on the bitness of EveryThing. I.e. if it is a 32-bit or 64-bit version.

Added to my TODO list.

Everything IPC is always 32bit (even on 64bit Everything).
Any reason why you need to know if Everything is 32bit or 64bit?

http://stackoverflow.com/questions/1418 ... -or-64-bit

[Gisle Vanem]

Everything IPC is always 32bit (even on 64bit Everything).

You mean because the windows handle is always 32-bit?

Any reason why you need to know if Everything is 32bit or 64bit?

A 32-bit EveryThing can return files in e.g. %SystemRoot%\sysnative which makes little sense to a 64-bit calling program.
So if the caller has a-priori knowledge of the bitness of EveryThing, it can ignore such values. Or do you have a better suggestion?

[void]

You mean because the windows handle is always 32-bit?

Yes.

A 32-bit EveryThing can return files in e.g. %SystemRoot%\sysnative which makes little sense to a 64-bit calling program.
So if the caller has a-priori knowledge of the bitness of EveryThing, it can ignore such values. Or do you have a better suggestion?

Everything should ignore any 32/64bit system redirection.

[jakel]

I have a question regarding IPC with Everything. The command line utility "es.exe" seems like a great idea. I use Cygwin on Windows. If I use ssh to connect to a machine, I have a problem using "es.exe". I get the following error message on calling it:

Everything IPC window not found, IPC unavailable.

Now it seems that Cygwin is using some complex setup to make ssh work with newer Windows versions: The configuration script "ssh-host-config" for setting up the ssh server adds two additional users: One for the service and one for using setuid for settings permissions. I suspect that this is the reason that IPC is not working.

Anyway, it seems that this setup will not work with es.exe, but it seems like a prime scenario for using the command line version of everything. What is the suggested solution to this problem? I guess one could somehow try to wrap es.exe with a different mechanism than IPC, but maybe there is a better way? Everything itself also runs a service, so maybe this could point to a potential solution?