Thanks for that idea Mike!
On Aug 23, 2017 10:07 PM, "Mike Bonner via use-livecode" <
use-livecode@lists.runrev.com> wrote:
> If things don't work as well as you like, and you decide to go with
> sockets, (and you are ok with running a small server process) chatrev is
> cool, is already built,
If things don't work as well as you like, and you decide to go with
sockets, (and you are ok with running a small server process) chatrev is
cool, is already built, and should be easy to modify to do what you want.
(Its already set to distribute messages from clients to the server then out
to the
i understand. Thats exactly what I am I am going with ease of
implementation.
the list of files would be obtained using "the files" function of livecode
. from a mapped drive on a LAN.
Thats what I am thinking. it should all be ok .. i hope the OS
caches to memory the folder
So you would be using sockets to send a list of 1 or more file names
(notifications) across the network to other computers?
If so, I am not sure there is any significant performance difference
than having the notifications in a database.
The only practical difference may be the ease of
like for example
inv-fileidhash.not would mean "invitation to file with that ID" but
having been placed in a particular user's notification folder, it would
know the notification is for that user and no other.
make sense?
On Wed, Aug 23, 2017 at 8:55 PM, Tom Glod
by notification I don't mean anything fancy or OS or network based...just a
notification system that shows to the user "so and so has invited you to a
file"... defined entirely by me.
the code in the filename is pre-defined, they would all be lower case and
under x amount of characters.
my
On 8/23/2017 4:25 PM, Tom Glod via use-livecode wrote:
> Hi folks, I'm building a notification systemand I don't want to add
> another DB query to the systemso my idea is to save notifications as a
> file in a folder, and the just read and process "the files"
>
> so the name of the
Hmm… by notifications do you mean IPC? Is this over the network or multiple
processes on a single machine. For both cases sockets is probably easiest. On
the single machine then you can just accept on localhost to avoid getting
firewall dialogs:
local sPort
set the defaultNetworkInterface to
Hi folks, I'm building a notification systemand I don't want to add
another DB query to the systemso my idea is to save notifications as a
file in a folder, and the just read and process "the files"
so the name of the file would contain the notification data i wouldn't
have to