$arr_19 ), array( 3, false, $arr_20, $arr_24 ), array( 2, false, "\" />", $arr_25 ) ) ); ?> $arr_27 ), array( 3, false, $arr_28, $arr_30 ), array( 2, false, "\" />\n\n", $arr_31 ) ) ); ?> array( 2, false, false, $arr_9 ), array( 4, $arr_10, "if", $arr_245, $arr_248 ), array( 2, false, "\n", $arr_249 ) ) ); ?> rr_466 ), array( 4, $arr_467, "if", $arr_482, $arr_484 ), array( 2, false, "\n", $arr_485 ) ) ); ?> A Sticky Mess » Linux Magazine
 

Interoperability and code reuse

A Sticky Mess

Author(s):

Developing cross-platform apps can be difficult and error prone. We offer some tips to ease the work.

Interoperability is a good thing; it enables us to use security tools across multiple platforms (like OpenID and OSSEC) and combine data from multiple platforms into tools like Prelude, right? Code reuse is also good – why reinvent the wheel if someone is giving away really nice all-weather tires? Unfortunately, when it comes to interoperability, not everyone does a good job of implementation. In fact, efforts to achieve compatibility and interoperability often can make a real security mess.

Read full article as PDF »

056-057_kurt.pdf (1,006.06 kB)
comments powered by Disqus

Direct Download

Read full article as PDF »

056-057_kurt.pdf (1,006.06 kB)

News