If it's worth protecting no matter what the medium it's worth encrypting further with something like IPSec and some certificates with a damn high key length... Our site to site wireless links are using WPA2 from bridge device to bridge device, but even before the traffic hits the link it has been shoved into an IPSec tunnel. Treat any wireless link as "Public" even if it has encryption; VPN or Tunnel is the only way.
I wouldn't necessarily call using a framework code re-use per se; more code generation... I'll admit that it is using someone elses code, but as you have found out, frameworks usually have pretty tight limitations (which is fine if you have a project that you know will not have a requirement change in it's lifetime), either that or they attempt to allow for everything and as such become more complex and messy than simply using the language in a vanilla form.
Great programmers build themselves job specific factories, classes, modules, includes (whatever container you use in your specific lingo) and re-use them in other applications... Teams of great programmers build themselves a communcal collection of packaged code and libraries which perform the common business logic or UI elements frequently used in that company or group:)
Slashdot Mirror
If it's worth protecting no matter what the medium it's worth encrypting further with something like IPSec and some certificates with a damn high key length... Our site to site wireless links are using WPA2 from bridge device to bridge device, but even before the traffic hits the link it has been shoved into an IPSec tunnel. Treat any wireless link as "Public" even if it has encryption; VPN or Tunnel is the only way.
I wouldn't necessarily call using a framework code re-use per se; more code generation... I'll admit that it is using someone elses code, but as you have found out, frameworks usually have pretty tight limitations (which is fine if you have a project that you know will not have a requirement change in it's lifetime), either that or they attempt to allow for everything and as such become more complex and messy than simply using the language in a vanilla form. Great programmers build themselves job specific factories, classes, modules, includes (whatever container you use in your specific lingo) and re-use them in other applications... Teams of great programmers build themselves a communcal collection of packaged code and libraries which perform the common business logic or UI elements frequently used in that company or group :)
I have never seen such a complete reference for a language as the MSDN references for C# and VB .Net.