Yes, storing state info in your database will slow things down (whether or not the penalty incurred is acceptable is up to you.)

Maybe I don't understand the problem, but I can't see what difference it makes which server the user uses. Say you send in your text to server A and it sends it back with some suggestions for the misspellings. Then you send the (possibly corrected) text to server B to be written to the database. So what? I don't see a problem with that.

What I would do is have an html form with two submit buttons -- one to spell check and one to commit the text to the database. That way you can spell check to your heart's content and then commit (with possible misspellings) whenever you're ready.

In reply to Re: spell checking by eg
in thread spell checking by boingolover

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.