"Madam President" is one fiction book which kept me entranced, racing to finish because I wanted to know what happened to the characters and find out exactly how this tale of two sexes would end. Each character was quite distinct. Ordinarily I don't do fiction. My favorites are biographies and history books.

Here is one literary work which warns us what can happen when society's mores swing too far one direction or another. The author's story is a pendulum parody and it reflects what can happen when things go too far one way or the other. Obviously, the pendulum swings both ways. ....Since our history seems to go in waves, it's good to have a futuristic novel based on current issues being played out in today's society.

A story which fixated me right to the chair until I finished it. Now, I'm sorry it's finished because I so enjoyed the mental sensation of peeking into the lives of the characters. I believe the author exhibits a great perspective of the whole country, understands what's colloquial where and who's what in what region of the United States. I like the fact that the Truckers were portrayed the way they are and it sure did my heart good to have those Hudnuts get their come-uppence.

It would be a great book for a movie. I could visualize everything as I went. It seems to be difficult sometimes to do that with a book. Either the author doesn't have a good handle on the location s/he is writing about or else they don't know how to relate that to the reader.

Hall made the characters and the action seem quite real. He made me remember the characters and either hate them or love them, as it should be. I could 'hear' them talk in their drawls when appropriate. I sure did find a lot of modern day speech that I recognized and felt that this author is doing for our time what other great writers [Dickens, Melville...] did for their time: capture the flavor of the speech used at the time the book was written.

Oh, boy, Wesley Hall, you sure do write a mean tale!

I read Mighty gents over four years ago and I have been searching for it ever since. Mr.Wesley wrote an excellent story about the struggle for acceptance and survival and made it touch those of us who knew people just like those in his script.

Mighty Prevailing Prayer is a fantastic read! It explains in detail what must done in order to gain the answer in prayer. It, and The Complete Works of E.M. Bounds on Prayer are two of the most comprehensive volumes I've ever read on prayer. If you want to know the secrets of how to prevail with God, and over satan, then this book is a must have; it comes highly recommended!!!

I plan to get the Misty books for my daughters when they're old enough...Ms. Henry gave Misty life, and her books are a must for any young person undergoing their animal loving phase...and even for those who don't love animals! They are a good read all around, and I wouldn't hesitate to recommend them to the children of friends.

This is an excellent book dealing with the Holy Spirit, the Spirit filled-life, and the empowering and annointing of the Spirit. This is an excellent book for group study. This book was truly written by one who is annointed and filled with God's Holy Spirit.

"Moving in the Wrong Direction" is a book of encouragement. It is a very detailed study and clear interpretation of the book "Jonah". After reading this book, I am much more encouraged and committed to moving in the direction that God wants me to go. This book gives excellent reasons and examples about what can and will happen, if we don't follow God's instructions. "Moving in the Wrong Direction" tells about the trails and tribulation we bring on ourselves when we don't do what God wants us to do. I love the simplicity with which the book is written, yet it gives profound and in depth explanations and interpretations about "Jonah". I just love it, and think it is Dr. Wesley's best book.

Before reading this book a few years ago, I had been programming in C++ and had yet to really realize reusable software. The excellent thing about this book is that from start to finish, the focus is consistently placed on creating a reusable library of data structures. As such, this is one of the only books I've ever purchased from which I've walked away not only better informed but with immediately useful code developed along the way.

Though the book uses the Eiffel language, it should be easy for folks used to other languages to approach. Much to his credit, Gore takes the time in the beginning of the book to basically hand hold the reader through the code and the exercises. As the book progresses, with each chapter building on the last, Gore gives the reader greater autonomy, until the text centers more on the theory of data structures than the source needed to represent them. I found this approach extremely effective, and wish that more computer books were written in the same fashion.

I've since read a number of books on data structures and OO for a variety of computer languages. If I had to pin down the text that was most useful to me in not only understanding the subject matter but also gaining deeper insights into reusability, it would definitely be this book. I can't recommend it highly enough!

This book was a breath of fresh air! Something everyone needs sitting on their bookshelf at home! The world will be reconstructed and revived due to this book! Wes White did it again

I would like to review about the Press Conference Proceeding

The computing world is full of zealots and bigots. Mac vs. DOS. Ethernet vs. Token Ring. Unix vs. VMS. And TCP/IP vs. OSI. It's like discussing religion, or politics. David Piscitello and Lyman Chapin have to deal with these arguments every day. Open Systems Networking: TCP/IP and OSI (Addison-Wesley, 1993) is their attempt to bring some facts and background into the discussion. Anyone interested in learning the real truth about OSI, its relationship to TCP/IP, and why things are the way they are should be interested in this book. It's a long overdue work, and they've pulled it off beautifully: no other author has explained the two protocol suites, in parallel, understandably and truthfully, as well as Piscitello and Chapin have.

If you've been disappointed in other books claiming to "explain" OSI, you'll find Open Systems Networking a refreshing change. It doesn't have the mindless repetition of tables and rewording that William Stallings' books do, nor the "gee this looks dumb" attitude of Marshall Rose's. Piscitello and Chapin served on the national and international standards committees responsible for developing most of the OSI standards. They were there. They know what the standards meant to say, where the bodies are buried, and how to put them all in context. That lets them compare, contrast, explain, and evaluate both OSI and TCP/IP in an honest and straightforward way. Their point of view is a technical one, and not a political one. They advocate the best technology to solve a problem.

Open Systems Networking is written for the educated networking professional. It is assumed that the reader has a passable knowledge of TCP/IP. The obligatory presentation of the OSI reference model is at once brief, humorous, and insightful. Most importantly, the explanations of the OSI standards don't get bogged down in explaining trivial details of state machine and protocol header. This is not a book for bit-jerkers. Instead, Piscitello and Chapin focus on the truly important aspects of each standard, identifying what is significant, what is useless, and why it all turned out this way.

The discussion of ASN.1, the all-important language for encoding data use in both ISO and some TCP/IP standards is a good example. Half of the space is devoted to a discussion of concepts and reasons why such an encoding is a good idea, as well as a discussion of problems that have occurred in systems that didn't have such an encoding. The other half gives just enough explanation to let an interested reader understand how to read ASN.1. The difference here is between reading a language and writing it. After reading Open Systems Networking, most people will know all they need to know about ASN.1.

Knowing that much of their audience will have some TCP/IP bias, Piscitello and Chapin go easier on the home team than they do with their own progeny. For example, when discussing why the OSI transport protocol has five classes (TP0 through TP4), they note: "The whole notion of typing network connections was myopic, ill- advised, and ultimately destructive." They are a bit less caustic when discussing the chaos of routing in TCP/IP networks, pointing out that "RIP is the routing protocol ``we love to hate'' ... HELLO is another open routing protocol that has seen better days."

If you've got an open mind, pick up a copy of Open Systems Networking. It's a readable history of the development of networking and well worth reading. If you're one of those protocol bigots I keep running into ... pick up a copy anyway.