I didn't see it in the chapter list, so probably not, but is there anything in your book about writing (good) tests?
That's covered of the Chapter 18, which has a Secret Chapter Title.
Our Django Book is Launched
21–30 of 136 posts
Re: Our Django Book is Launched
#22Will this be available on Google Books? I'd like to keep all my purchases in one place, plus I prefer the reflow-ability over a PDF.
What format does Google Books require?
Re: Our Django Book is Launched
#23One of my big concerns is user / session security. I have tried to follow and reason through discussions on stackoverflow and much of tpatchek's notes. I would be interested in how "high level" the security chapter is from anyone who has shelled out already. For example I assume I will 1. only use persona or openid (avoids storing passwords in my servers thus making a lot of things much much easier) 2. sessions - sto…
Your 2nd point has significant performance implications, so I wouldn't take that for granted.
Your 1st point is pretty controversial and has significant UX implications. Using OpenID instead of just the built-in Django auth or bcrypt is hardly "much much easier" either, it's far more complex to integrate.
Re: Our Django Book is Launched
#24Will it be available on the Kindle or as an ePub or solely PDF and print?
I'm one of the authors. Because of the formatting issues of Kindle and ePub, the negative reviews Python books get when formatting breaks in those formats, we're not sure yet it we'll publish it in mobi/epub. That said, if you have any advice on getting Python to look good in those formats, we would love to hear it. :-)
Purchased.
But agreed that a epub version to read on my kobo would be awesome !
Re: Our Django Book is Launched
#25Is it only for 1.5? Will the best practices carry over for someone looking to understand more about structuring 1.4 projects?
I'm working on a 1.4 project right now and while 1.5 sounds great, I'm not sure we're quite ready to upgrade. But we've been looking for a best practices book more recent than the ones covering 1.0 on amazon.
Re: Our Django Book is Launched
#26Will this be available on Google Books? I'd like to keep all my purchases in one place, plus I prefer the reflow-ability over a PDF.
What format does Google Books require?
Looks like ePub if you're going to add re-flowing text (I see in the other thread what a pain that can be, but I think it works fine for Programming Python which I have through Google Books).
They also support PDF, which I'd still prefer to purchase through Google directly if only to keep my stuff in one place.
http://support.google.com/books/partner/bin/answer.py?hl=en&...
http://support.google.com/books/partner/bin/answer.py?hl=en&...
Re: Our Django Book is Launched
#27I purchased this book because Audrey and Danny put on great events in LA area. I've been to one of them and they were extremly helpful and the event was great :)
I'm sure the book has a ton of useful information and I will definitely be reading it.
You should purchase the book if you believe in giving back to the people who give there time to open source and helping others.
Thanks again, Fernando
Re: Our Django Book is Launched
#28One of my big concerns is user / session security. I have tried to follow and reason through discussions on stackoverflow and much of tpatchek's notes. I would be interested in how "high level" the security chapter is from anyone who has shelled out already. For example I assume I will 1. only use persona or openid (avoids storing passwords in my servers thus making a lot of things much much easier) 2. sessions - sto…
Your 2nd point has significant performance implications, so I wouldn't take that for granted. Your 1st point is pretty controversial and has significant UX implications. Using OpenID instead of just the built-in Django auth or bcrypt is hardly "much much easier" either, it's far more complex to integrate.
I don't think the 2nd point has significant performance implications. If you're not serving up static pages then there's always network calls to be made on the backend.
Storing a nonce on the client and looking everything up on the backend is an easy solution which means you don't have to worry about what data you're storing and if that'll be available in the browser.
I think it's cheaper to optimize on the backend for a simpler (and safer) solution.
Re: Our Django Book is Launched
#29One of my big concerns is user / session security. I have tried to follow and reason through discussions on stackoverflow and much of tpatchek's notes. I would be interested in how "high level" the security chapter is from anyone who has shelled out already. For example I assume I will 1. only use persona or openid (avoids storing passwords in my servers thus making a lot of things much much easier) 2. sessions - sto…
Disclaimer: I'm one of the authors.
The book covers 7 pages that gets you started down the road of understanding security. We provide you the stuff you have to know, and point you towards better resources.
Keep in mind we aren't professional security experts. If your site needs to be that secure, the best thing you can do is to hire the services of a carefully vetted security expert.
Re: Our Django Book is Launched
#30One of my big concerns is user / session security. I have tried to follow and reason through discussions on stackoverflow and much of tpatchek's notes. I would be interested in how "high level" the security chapter is from anyone who has shelled out already. For example I assume I will 1. only use persona or openid (avoids storing passwords in my servers thus making a lot of things much much easier) 2. sessions - sto…
I'm not sure what this has to do with the focus of the book, Django has session support so I doubt a book about Django would fully cover re-writing one of its components. Django used to only be able to store nothing in the session cookie other than the ID so that part can definitely happen (new in Django 1.4 are Cookie Based Sessions that used signed cookies to store data in cookies, but it's something you have to turn on).
This is all fully documented, if you're curious you should read it.
https://docs.djangoproject.com/en/1.5/topics/http/sessions/
As for tying into OpenId or other similar systems, it's a piece of cake. There are numerous Django apps out there to accomplish it. I have used django-social-auth for a project and had no problems getting things running: