notifications system using "the files"? bad idea?

Tom Glod tom at
Wed Aug 23 20:58:17 EDT 2017

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 <tom at> wrote:

> 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 question is whether there is some kind of bottle neck that I am not
> aware of that could prevent a LAN to send "the files" list to multiple
> clients quickly...or more quickly than a DB query for records that match a
> certain query.
> Thanks guys....
> On Wed, Aug 23, 2017 at 4:40 PM, Paul Dupuis via use-livecode <
> use-livecode at> wrote:
>> On 8/23/2017 4:25 PM, Tom Glod via use-livecode wrote:
>> > Hi folks, I'm building a notification system....and I don't want to add
>> > another DB query to the 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 read each file, just the list of files in the folder.
>> >
>> > hoping to save some network traffic that way.
>> >
>> > am I gonna regret this?...hit some kind of OS bottleneck?..... anybody
>> have
>> > any ideas why this would be a bad idea?
>> >
>> > we build for all 3 desktop platforms.
>> >
>> > Thanks for any thoughts.
>> >
>> Are the notifications (i.e the file names) preset? Or user entered. If
>> user entered, realize that there are issues with converting file names
>> across platforms. Linux, OSX, and Window have different reserved
>> characters and file name standards, as well as different support for
>> Unicode or high-ASCII characters. If all you messages are basic ASCII
>> characters and under about 250 characters in length, you should be fine.
>> _______________________________________________
>> use-livecode mailing list
>> use-livecode at
>> Please visit this url to subscribe, unsubscribe and manage your
>> subscription preferences:

More information about the Use-livecode mailing list