Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the acf domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/bailey/public_html/wp-includes/functions.php on line 6131

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the astra-addon domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/bailey/public_html/wp-includes/functions.php on line 6131

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the fl-builder domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/bailey/public_html/wp-includes/functions.php on line 6131

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the uabb domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/bailey/public_html/wp-includes/functions.php on line 6131

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the updraftplus domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/bailey/public_html/wp-includes/functions.php on line 6131

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wordpress-seo domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/bailey/public_html/wp-includes/functions.php on line 6131

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the astra domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/bailey/public_html/wp-includes/functions.php on line 6131

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the astra-addon domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/bailey/public_html/wp-includes/functions.php on line 6131

Warning: Cannot modify header information - headers already sent by (output started at /home/bailey/public_html/wp-includes/functions.php:6131) in /home/bailey/public_html/wp-content/themes/robintek-child-theme/functions.php on line 48

Warning: Cannot modify header information - headers already sent by (output started at /home/bailey/public_html/wp-includes/functions.php:6131) in /home/bailey/public_html/wp-content/themes/robintek-child-theme/functions.php on line 49

Warning: Cannot modify header information - headers already sent by (output started at /home/bailey/public_html/wp-includes/functions.php:6131) in /home/bailey/public_html/wp-content/themes/robintek-child-theme/functions.php on line 50

Deprecated: Function WP_Dependencies->add_data() was called with an argument that is deprecated since version 6.9.0! IE conditional comments are ignored by all supported browsers. in /home/bailey/public_html/wp-includes/functions.php on line 6131
John Marsh Addresses Avoiding Costly Litigation in Latest Blog Post: - Bailey Cavalieri

John Marsh Addresses Avoiding Costly Litigation in Latest Blog Post:

Another Idea for Improving the Defend Trade Secrets Act: Providing an “Off Ramp” to the Plaintiff Who Wants to Avoid a Costly Litigation
In a post last year, I proposed a solution for a recurring problem in trade secret litigation–namely, the situation where a former employee takes information but quickly regrets their conduct and looks for a way to resolve the dispute. As readers will recall, I proposed a “safe harbor” that would allow that former employee to provide disclosures and an injunction to address their former employer’s legitimate concerns. After my post, several colleagues, including my friends and fellow trade secret travelers Russell Beck and Mark Klapow, noted a potential dilemma for a trade secret owner. They suggested that I should consider a similar protection for plaintiffs whose suspicions about trade secret misappropriation never fully materialize or who face litigation costs that outstrip that litigation’s utility. To afford protection to those trade secret owners, this post proposes an “off ramp” procedure early in a trade secret dispute that would hopefully alleviate those situations.

Continue Reading

April 2024

Authors
John Marsh
Member
Service Affiliation
Share
Scroll to Top