Howdy

I tested this approach with 2-3 users simultaneously and it worked. In the real life there would be up to 20 maybe 30 users who would work with this program and probably some of them would start the packed Perl/Tk front-end simultaneously.

Benchmark? That is simulate a 100 users or a 1000 users and see what happens, poke holes in your program, find the squeaky wheel in your design

Are there any pitfalls on this approach?

kinda -- people forget to test for pitfalls, so what may be regular sameness surprises them and they call it pitfall :D

Are there any limits to the number of users who can simultaneously execute a packed Tk script?

Yes, everything has limits :)

If all the users are sharing the server, and all the perl/par is being written to the server (%temp% is on server), then you're limited by server cpu/ram and disk ... 20-30 users/instances seems very very very low

I realize this sounds very generic, but that is the essence/details of the question, sqlite has writeups on performance metrics, Tk is only limited by cpu/ram, par is limited by PAR_TEMP...

go learn how these apply to your setup

In reply to Re: Simultaneous access to the tk script (details pitfalls) by Anonymous Monk
in thread Simultaneous access to the tk script by Anonymous Monk

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.