P4 Blog

  • May 20, 2015

    Python 2.5 gained the with statement in 2005, implementing PEP 343. The statement was designed to factor out the use of try-finally blocks and is often used to control the use of resources. A standard idiom, for example, is to use a with block when opening a file:

      with open(“somefile.txt”,”r”) as f:
    	  content = f.read()
    Posted In:
  • May 19, 2015

    May 20 Webinar Shows How to Stop Data Theft

    There’s been a lot of interest in our new Helix Threat Detection capability, which runs behavioral analytics against our granular log data to uncover and prioritize “anomalous user behavior.” In a nutshell, that means you can see if someone’s doing something they’re not supposed to with regard to your intellectual property. Like, say… stealing it. 

    Posted In:
  • May 14, 2015

    I recently delivered a series of live webinars in different time zones around the world. The webinars were called “Introducing Helix,” and, as you'd guess from the title, they were overviews of our recently launched SCM and collaboration platform. They were successful in that we had big audiences that stayed until the Q&A sessions and asked thoughtful questions. It was clear we'd piqued their interest!

    Posted In:
  • May 13, 2015

    This week we released P4Connect 2.7, the latest round of improvements to our free and Open Source integration with Unity. Since our previous release a few months back, we've gotten a lot of great feedback. We’ve had discussions in the forums and the Perforce Workshop, received feedback in the Unity Asset Store, and conducted multitudes of onsite visits with customers. After hours of talking to the Unity+Perforce community, we were inspired to make several enhancements:

    Posted In:
  • May 11, 2015

    Our Cygwin license has expired and due to the low demand for Cygwin platform builds we are not renewing it. All Cygwin builds have been pulled from our site in compliance with the license. However if you are a stalwart fan of Perforce and Cygwin all is not lost! Let’s look at your options.

    Using the Windows p4:

    There is a function that many folks in the Perforce community have used for awhile now to avoid installing two p4 executables on their machine. In Cygwin you can add the following function to your .bashrc:

    p4() { PWD=$(cygpath -wa .) "/cygdrive/c/Program Files (x86)/Perforce/p4" "$@"; }

    This will allow you to use the regular Windows build of p4 from inside of Cygwin.

    Posted In:
  • May 07, 2015

    Last year I published a blog article Lightning Fast Syncs where I described how to improve the performance of p4 sync when there was network latency involved. The abbreviated version is that we enabled compression, increased the network buffer sizes, and fetched files in parallel. The tests included a mix of text and binary files totaling 135MB with 140ms latency. I think it served as a very good reason to upgrade.

    Posted In: