Posts

Showing posts from September, 2014

Websites for Advanced Level Java Developers

Image
1. Stackoverflow Stackoverflow.com is probably the most popular website in the programming world. There are millions of good questions and answers. Learning an API or a programming language often rely on code examples, stackoverflow has a lot of code segments. Another good thing about stackoverflow is that it is social. You can view questions under some certain tags, e.g. “java” and “regex”, then you can see what question is most frequently asked and most voted. This can serve as a good resource for learning, also a good resource to write popular topics of Java bloggers. URL: http://stackoverflow.com/

What should every programmer know about security?

Principles to keep in mind if you want your applications to be secure:Never trust any input!Validate input from all untrusted sources - use whitelists not blacklistsPlan for security from the start - it's not something you can bolt on at the endKeep it simple - complexity increases the likelihood of security holesKeep your attack surface to a minimumMake sure you fail securelyUse defence in depthAdhere to the principle of least privilegeUse threat modellingCompartmentalize - so your system is not all or nothingHiding secrets is hard - and secrets hidden in code won't stay secret for longDon't write your own cryptoUsing crypto doesn't mean you're secure (attackers will look for a weaker link)Be aware of buffer overflows and how to protect against them

50 Cheatsheets For Programmers And Developers

1. Asynchronous JavaScript And XML (AJAX): This is a group of interrelated web development techniques that are used to create asynchronous web applications on the client side.

5 things you didn't know about everyday Java tools

1. StAX When XML first appeared on most Java developers' radar, back around the turn of the millennium, there were two basic approaches to parsing XML files. The SAX parser is essentially a giant state machine of events fired back at the developer via a series of callback methods. The DOM parser pulls the entire XML document into memory and slices it up into a series of discrete objects, which are linked together to form a tree. The tree describes the entire XML Infoset representation of the document. Both parsers had their drawbacks: SAX was too low-level to use, but DOM was too expensive, particularly for large XML files — the whole tree got to be a pretty hefty heap hog.

5 things you didn't know about Java Database Connectivity

Many Java developers today know the Java Database Connectivity (JDBC) API by way of a data-access platform such as Hibernate or Spring. But JDBC is more than a background player in database connectivity. The more you know about it, the more efficient your RDBMS interactions will be. I'll demonstrate several of the newer features introduced between JDBC 2.0 and JDBC 4.0. Designed with modern software development challenges in mind, these features support application scalability and developer productivity — two of the common challenges facing Java developers today.

5 things you didn't know about multithreaded Java programming

While few Java™ developers can afford to ignore multithreaded programming and the Java platform libraries that support it, even fewer have time to study threads in depth. Instead, we learn about threads ad hoc, adding new tips and techniques to our toolboxes as we need them. It's possible to build and run decent applications this way, but you can do better. Understanding the threading idiosyncrasies of the Java compiler and the JVM will help you write more efficient, better performing Java code. I introduce some of the subtler aspects of multithreaded programming with synchronized methods, volatile variables, and atomic classes. My discussion focuses especially on how some of these constructs interact with the JVM and Java compiler, and how the different interactions could affect Java application performance.

Learn MYSQL in 40 mins

Image
This video tutorial cover: 

creating / destroying databases, creating / destroying tables, data types, NULL, DEFAULT, ENUM, AUTO_INCREMENT, primary keys, foreign keys, atomic data, normalized, DESCRIBE, INSERT, ALTER, SELECT, SHOW, RENAME, WHERE, logical operators, comparison operators, ORDER BY, GROUP BY, LIMIT, string operators, joins, LIKE, DISTINCT, math functions and more.

Learn Java in 30 Mins

Image
This video specifically cover the following topics: 
primitive data types, comments, class, import, Scanner, final, Strings, static, private, protected, public, constructors, math, hasNextLine, nextLine, getters, setters, method overloading, Random, casting, toString, conversion from Strings to primitives, converting from primitives to Strings, if, else, else if, print, println, printf, logical operators, comparison operators, ternary operator, switch, for, while, break, continue, do while, polymorphism, arrays, for each, multidimensional arrays and more.

Tutorial By: Derek Banas
Source : newthinktank

For Code used inn this tutorial  CLICK HERE!

5 things you didn't know about JARs

For most Java developers, JAR files and their specialized cousins, WARs and EARs, are simply the end result of a long Ant or Maven process. It's standard procedure to copy the JAR to the right place on the server (or, more rarely, the user's machine) and forget about it. Actually, JARs can do more than store source code, but you have to know what else is possible, and how to ask for it. The tips in this installment of the 5 things series will show you how to make the most of Java Archive files (and in some cases WARs and EARs, too), especially at deployment time. Because so many Java developers use Spring (and because the Spring framework presents some particular challenges to our traditional use of JARs), several of the tips specifically address JARs in Spring applications.

How does SSL/TLS work?

General SSL (and its successor, TLS) is a protocol that operates directly on top of TCP (although there are also implementations for datagram based protocols such as UDP). This way, protocols on higher layers (such as HTTP) can be left unchanged while still providing a secure connection. Underneath the SSL layer, HTTP is identical to HTTPS. When using SSL/TLS correctly, all an attacker can see on the cable is which IP and port you are connected to, roughly how much data you are sending, and what encryption and compression is used. He can also terminate the connection, but both sides will know that the connection has been interrupted by a third party. In typical use, the attacker will also be able to figure out which host name you're connecting to (but not the rest of the URL): although HTTPS itself does not expose the host name, your browser will usually need to make a DNS request first to find out what IP address to send the request to. High-level description of the protocol Aft…