Wrox Programmer Forums

Need to download code?

View our list of code downloads.

Go Back   Wrox Programmer Forums > Wrox Announcements and Feedback > Wrox Book Feedback
Password Reminder
Register
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read
Wrox Book Feedback A forum to submit feedback on Wrox books if other forums on P2P have been unable to address your book-specific needs. IF YOU ARE LOOKING FOR CODE DO NOT ASK "Where can I find the code for this book?" That question is answered here.
Welcome to the p2p.wrox.com Forums.

You are currently viewing the Wrox Book Feedback section of the Wrox Programmer to Programmer discussions. This is a community of tens of thousands of software programmers and website developers including Wrox book authors and readers. As a guest, you can read any forum posting. By joining today you can post your own programming questions, respond to other developers’ questions, and eliminate the ads that are displayed to guests. Registration is fast, simple and absolutely free .
DRM-free e-books 300x50
Reply
 
Thread Tools Search this Thread Display Modes
  #1 (permalink)  
Old June 18th, 2003, 03:21 PM
Registered User
 
Join Date: Jun 2003
Location: Attleboro, MA, USA.
Posts: 1
Thanks: 0
Thanked 0 Times in 0 Posts
Default VB.Net Handbook Threading

Chapter 1 is a big disappointment. Who ever wrote this doesn't know how preemptive OSes work let alone Windows.

The several errors include (at least):

   1. SPawing a new thread in a process is not "free thrading." p.10

   2. VB6 did not create a new process to create a thread. p.11

   3. Figure 3 (p.11) is not a diagram of apartment threading. You can have apartment theads in a single process.

   4. Windows does not place an instruction in a thread's execution sequence to determin how long a thread should run. (p.15)

   5. Interupts are not placed on a thread's stack (p.16)

   6. The discussion of thread priority does not mention that starved threads get a priotity boost. (p.18) Yet an advanced topic like processor affinity is discussed on p.13!

Whowever wrote this seems really confused about a .Net process and an OS process but in the introductory material he's clearly discussing the OS process (or so it seems.) No disccusion of .Net Process islation?

I really expect (and usually get more) from a WROX book. This book was poorly reviewed for technical content (at least Chapter 1.) AS I read on, I hope they know more about .Net threading than OS kernel thread, processes, and interrupts.
Reply With Quote
  #2 (permalink)  
Old June 18th, 2003, 03:28 PM
Friend of Wrox
Points: 3,489, Level: 24
Points: 3,489, Level: 24 Points: 3,489, Level: 24 Points: 3,489, Level: 24
Activity: 0%
Activity: 0% Activity: 0% Activity: 0%
 
Join Date: Jun 2003
Location: Central, NJ, USA.
Posts: 1,102
Thanks: 0
Thanked 2 Times in 2 Posts
Default

It should be noted that Wiley didn't buy any of the Wrox "Handbooks". I would expect Apress has them and errata should be directed to them.


Hal Levy
Daddyshome, LLC
NOT a Wiley/Wrox Employee
Reply With Quote
Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Trackbacks are Off
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Visual Basic .NET Threading Handbook e_sham All Other Wrox Books 2 August 11th, 2008 02:49 PM
VB.Net Scalability Handbook ejbrown All Other Wrox Books 0 October 3rd, 2005 02:24 AM
Where is the code of "c# threading handbook" netbit All Other Wrox Books 1 June 22nd, 2004 12:10 PM
VB.NET Deployment Handbook billsox Wrox Book Feedback 2 August 28th, 2003 04:03 PM
Visual Basic .Net Deployment Handbook MainSoft Wrox Book Feedback 1 June 21st, 2003 09:32 AM



All times are GMT -4. The time now is 01:25 PM.


Powered by vBulletin®
Copyright ©2000 - 2019, Jelsoft Enterprises Ltd.
© 2013 John Wiley & Sons, Inc.