Jira (PUP-3523) Scope work required to override environment caching behavior

[Christopher Price (JIRA)]

Title: Message Title

Christopher Price commented on an issue   Re: Scope work required to override environment caching behavior Also--I looked into the option of having a file system watcher that could automatically detect changes on the file system and invalidate the cache. This is definitely doable; recent JVMs have hooks into OS-level notifications for this, and Oracle provides a fairly complete example here: http://docs.oracle.com/javase/tutorial/essential/io/examples/WatchDir.java However, that solution is a bit more complex, and since we are wanting to move towards more explicit user-driven workflows for rolling out code, we're just going to go with the API approach for now. Add Comment   Puppet / PUP-3523 Scope work required to override environment caching behavior In SERVER-22, there was a lot of discussion about environment caching and how the cached values can look different from one request to the next if they are routed to different JRuby instances / passenger workers. One of the outcomes of that discussion was the proposal that we create some kind of mechanism in Puppet Server that is akin to the passenger ... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.