At a high level, please, what are the distinctions between these four terms.
Everything Service: I think of this as a little program that runs in the background, and performs various tasks on behave of Everything.exe, where Everything.exe is of course the general user interface that we all know and love.
Client Service: The closest I can get to here is another background job, but if so, aiding what part of Everything?
HTTP Server: a plugin that allows me to access lists of files and optionally, download those files, to an external device that exists outside the computer whose file store is being accessed. Perhaps a mobile phone accessing a copy of a client's project documentation.
ETP Server: I have not a clue.
Thanks in advance for any high-level (generic) clarification. I'm really asking "How much of all this must I master to be able to obtain a list of files on my laptop?"
Cheers, Chris
Client service vs. Everything Service vs. ETP Server vs. HTTP server?
-
- Posts: 688
- Joined: Wed Jan 05, 2022 9:29 pm
Re: Client service vs. Everything Service vs. ETP Server vs. HTTP server?
Everything Service
A Service that provides the Everything Search client access to the NTFS Master File Table and USN Journal.
(Creating an index and monitoring volumes for changes)
Everything Service
Client Service
Run the normal Everything Search client UI as a service.
There's no accessible UI.
Allows the use of the HTTP Server, ETP/FTP Server and Everything Server as a service.
This is useful for running these services on Windows Server without the need to login.
Everything Client Service
HTTP Server
Access your Everything index remotely from a webbrowser.
HTTP Server
ETP/FTP Server
ETP is Everything Transfer protocol.
ETP is an extension of FTP.
Access a small window of your Everything index remotely from another PC running Everything.
Access your Everything index remotely from an FTP client.
ETP/FTP Server
Everything Server
Access your index remotely from another PC running Everything.
Everything Server
A Service that provides the Everything Search client access to the NTFS Master File Table and USN Journal.
(Creating an index and monitoring volumes for changes)
Everything Service
Client Service
Run the normal Everything Search client UI as a service.
There's no accessible UI.
Allows the use of the HTTP Server, ETP/FTP Server and Everything Server as a service.
This is useful for running these services on Windows Server without the need to login.
Everything Client Service
HTTP Server
Access your Everything index remotely from a webbrowser.
HTTP Server
ETP/FTP Server
ETP is Everything Transfer protocol.
ETP is an extension of FTP.
Access a small window of your Everything index remotely from another PC running Everything.
Access your Everything index remotely from an FTP client.
ETP/FTP Server
Everything Server
Access your index remotely from another PC running Everything.
Everything Server
-
- Posts: 688
- Joined: Wed Jan 05, 2022 9:29 pm
Re: Client service vs. Everything Service vs. ETP Server vs. HTTP server?
Void, a belated thanks for this. I shall use this response to frame a guide for what-the-user-needs-to-know in terms of operations, and what can remain a black box to the user, so there will be follow-on questions asking for confirmation of my understanding.
Thanks again, Chris