The Angular Mini-Book is a
guide to getting started with Angular. You'll learn how to develop a bare-bones application, test it, and
deploy it. Then you'll move on to adding Bootstrap, Angular Material, continuous integration, and authentication.
Spring Boot is a popular framework for building REST APIs. You'll learn how to integrate Angular with Spring Boot and use security best practices like HTTPS and a content security policy.
For book updates, follow @angular_book on Twitter.
The JHipster Mini-Book is a
guide to getting started with hip technologies today: Angular, Bootstrap, and Spring
Boot. All of these frameworks are wrapped up in an easy-to-use project called JHipster.
This book shows you how to build an app with JHipster, and guides you through the plethora of tools, techniques and options you can use. Furthermore, it explains the UI and API building blocks so you understand the underpinnings of your great application.
For book updates, follow @jhipster-book on Twitter.
I've written up a howto for implementing [Tomcat's Ant Tasks|TomcatAntTasks] and why they don't work for me. I've been requested by a few users to use them vs. my current <copy> method, but I don't see why I should. Please read the wiki page and help me out if you can.
The Hibernate team is looking for $1888 to buy hibernate.org from a commercial domain hoster.
The goal of this action is not to get us rich (and others poor ;), but only to buy the domain. To give you an impression on how much money is needed: Hibernate is downloaded 500 times every day. The Hibernate website has more than 15.000 pageviews and 1.500 visits each day. If we estimate that every 10th person downloading Hibernate donates a dollar, we can free this domain in a little more than one month!
I'll probably donate. While we're at it, is anyone willing to help us Roller developers buy roller.com for $15,000? ;-) This is down from $20,000 when I originally inquired. No word on how much for roller.org.
I did a bit of research today and have some links for you concerning gzip-compression and why you should be using it on your server. First of all, DevArticles has some good resources on compressing web output for Apache 1.3.x (using mod_gzip) and Apache 2.0.x (using mod_deflate).
In a WebRef article, HTTP Compression Speeds up the Web, I found that any browser that supports HTTP 1.1 also supports web compression.
Is Compression Built into the Browser?
Yes. Most newer browsers since 1998/1999 have been equipped to support the HTTP 1.1 standard known as "content-encoding." (although content encoding was included in the HTTP 1.0 spec: RFC 1945). Essentially the browser indicates to the server that it can accept "content encoding" and if the server is capable it will then compress the data and transmit it. The browser decompresses it and then renders the page.
Good stuff to know.
