Dr. Dobb's Journal - November 2007 - (Page 27)

d11zeid_p6db 9/10/07 11:04 AM Page 27 Perforce continued from page 25 Frameworks The three frameworks (see Table 4) we considered in the development of this software were: • Microsoft .NET Framework. • Java Native Interface (JNI). • Enterprise Java Beans (EJBs). Fast Software Configuration Management jobs. With the push model, the Master divides up the jobs by some predefined criteria and sends them to the Workers. With the pull model, the Master puts the jobs in some shared container and then waits for the tasks to be picked up and completed by the Workers (see Figure 3). One of the advantages of using the pull model is that the algorithm automatically balances the load. This is due to the simple fact that the set of work is shared, and the workers can pull work from the set at their own pace until there is no more work to be done. The pull model provides excellent load balancing regardless of Worker speeds and network variations. This algorithm also has good scalability. Framework Microsoft .NET In consideration of timeliness and saving costs associated with writing and debugging code, it is often advantageous to utilize as much existing code as possible in creating an application. Open source and vendor supplied code snippets can perform many common functions such as standard I/O socket management. This is one area where Java really excels and there are many of these Disadvantages Need to know C#. Known security issues. Limited to Windows. Complex API. No garbage collection. Platform dependent. Designed mainly with web applications in mind. Intended for larger systems than CodeGrid (has additional overhead that we don’t need). API is difficult to learn. Complex XML descriptors. 200,000 developers rely on Perforce to manage their code. Here’s what they’re saying “Perforce is absolutely the only tool I would trust to manage our source code.” Brief Comparison of Frameworks Advantages Class library functions available from Microsoft (with C#). Microsoft environment. Class library functions available. Allows cross-platform development. Class library functions available. Hides implementation complexity of RMI. Uses latest advances in efficient distributed computing development. Platform independent. Nick Triantos NVIDIA “Perforce has been a breath of fresh air; a product which does what it's supposed to do and does it well.” Java Native Interface (JNI) Enterprise Java Beans (EJB) Scott Buchholz Sybase “Perforce is the cornerstone of Monster’s software production lines.” Table 4: Frameworks. Mark Conway Monster Worldwide “The bottom line is that Perforce has proven itself to be a reliable platform for global development at Symantec.” Russell Jackson Symantec See for yourself Free evaluation at www.perforce.com Figure 1: CodeGrid network overview. November 2007 l www.ddj.com l Dr. Dobb’s Journal 27 http://www.perforce.com http://www.ddj.com

Table of Contents Feed for the Digital Edition of Dr. Dobb's Journal - November 2007

Contents Hmmmm Alia Vox Developer Diaries Developer’s Notebook Smart Compilers - But Smart Enough? Conversations Grid-Enabling Resource-Intensive Applications Distributed Computing: Windows and Linux Adobe AIR: Desktop/Web Convergence Transparency on Demand Reusable Associations Effective Concurrency The Agile Edge Swaine’s Flames

Dr. Dobb's Journal - November 2007

For optimal viewing of this digital publication, please enable JavaScript and then refresh the page. If you would like to try to load the digital publication without using Flash Player detection, please click here.