Image | |
EAN-13 | 9780727842206 |
Product Name | Double Life: A Love Story From Broadway To Hollywood |
Language | English |
Category | Book / Magazine / Publication |
Amazon.com | Buy on Amazon ~ 1936833026 |
Price New | 14.65 US Dollars (curriencies) |
Price Used | 5.26 US Dollars (curriencies) |
Width | 6.3 inches (convert) |
Height | 1.5 inches (convert) |
Length | 9.2 inches (convert) |
Weight | 27.2 ounces (convert) |
Author | Alan Shayne, Norman Sunshine |
Page Count | 400 |
Binding | Hardcover |
Published | 11/15/2011 |
Features | Used Book in Good Condition |
Long Description | Gay marriage is at the forefront of America's political battles. The human story at the center of this debate is told in Double Life: A Love Story, a dual memoir by a gay male couple in a 50 plus year relationship. With high profiles in the entertainment, advertising and art communities, the authors offer a virtual timeline of how gay relationships have gained acceptance in the last half-century. At the same time, they share inside stories from film, television and media featuring the likes of Marlon Brando, Katharine Hepburn, Rock Hudson, Barbra Streisand, Laurence Olivier, Truman Capote, Bette Davis, Robert Redford, Lee Radziwill and Frances Lear. We both grew up at a time when homosexuality was not even spoken about, the couple writes. There were certainly no books that could help a young person understand that two people of the same sex could build a happy, productive and loving life together. When we entered our 50th year, another same sex couple told us we were an inspiration , so we began to feel we had the responsibility to make what we ve experienced available to others. We also wanted to show people who were not gay that our life was not unlike theirs. We are all pretty much the same, so we deserve equal protection under the Constitution. Alan Shayne retired as President of Warner Brothers Television in 1986, following a career that included Broadway, playing opposite Lena Horne and spanned forty years. As a leading casting director, he worked on such films as Catch 22, All the President s Men and many others. At Warner Brothers, he shepherded such long-running television series as Alice, Night Court and The Dukes of Hazard. Norman Sunshine was a successful magazine illustrator in New York who went on to be a painter and sculptor whose works are in museums and in important collections. In the early years of his career, he was vice president, creative director of an advertising agency, and coined the phrase, What Becomes a Legend Most? as well as Danskins are not just for Dancing. He interrupted his painting career when Frances Lear asked him to spearhead Lear s Magazine in the 1980s. Upon the two men meeting in New York in 1958, We didn t want to live together, says Shayne. We didn t have any examples of what a good love relationship between two men could be. And there was always the problem of hiding so no one would know we were gay. There was no question that if I were known to be gay, living with another man, it would make it more difficult for me to get work as an actor. As an artist, Sunshine was able to maintain a moderately out lifestyle. But when the first exhibition of his paintings in New York brought on a profile in The New York Times in 1968, he was photographed in the apartment that he admitted sharing with Shayne. At both his advertising agency and Shayne s television production company, the article was met with absolute silence. Even in the 1970s, when Sunshine won an Emmy for the graphics and title design he had created for one of Shayne s television productions, Alan and I agreed it was not a good idea for us to be seen together at an industry event, he remembers. Alan, after all, was one of the very few homosexuals who had such a powerful, high profile job, and who lived openly with a man. Homophobia had its adherents and some ruthless climber up the executive ladder would certainly love an opportunity to use it... Better to be seen with a woman, we were advised by a very trusted friend, Makes everyone more comfortable. Happily, in 2008, the State of Massachusetts allowed the opportunity for the couple to be married on a beach in Nantucket. We were like a long, empty, closed-up house where the windows have just been opened, writes Shayne. The fresh air thrilled t |
Similar Items | 9780548021491: Secret Historian: The Life And Times Of Samuel Steward, Professor, Tattoo Artist, And Sexual Renegade 9780446563130: Eminent Outlaws: The Gay Writers Who Changed America 9780395837047: Arkansas: Three Novellas 9780374281342: Secret Historian: The Life And Times Of Samuel Steward, Professor, Tattoo Artist, And Sexual Renegade 9780312818234: Tricks: 25 Encounters 9780312030247: Parisian Lives (Stonewall Inn Editions) 9780226551913: Eminent Outlaws: The Gay Writers Who Changed America 9780140275681: Wisecracker: The Life And Times Of William Haines, Hollywood's First Openly Gay Star 9780062094490: Dropped Names: Famous Men And Women As I Knew Them 9780062094476: Dropped Names: Famous Men And Women As I Knew Them View 28 more similar items |
Created | 08-06-2013 12:18:22pm |
Modified | 04-30-2020 11:52:43pm |
MD5 | 8930d84ecb6ec103c3f83d59efe90003 |
SHA256 | b972484515d33729f21ecc546e58c32adb4e4521ac82c6b8249e695bf26fe9e8 |
Search Google | by EAN or by Title |
Query Time | 0.0279760 |
An article of interest
Making use of the tools we offer
Bulk Updates using the API
This feature started with version 3.3 of the API and it allows you to update many fields of a product in one call. Prior to this, each attribute for a product was updated in a separate call, causing the process to be a bit slow.
It is important to note that bulk updates only work with JSON formatted data. Because of this, you can leave the mode=json out of your call.
You should use a POST call instead of a GET to avoid over running the length limits that can be found when sending long URLs.
Required Parameters
- keycode - your normal API keycode
- update - the first product you intend to update (more info below)
- field - must be set to *bulk*
Optional Parameters
- test - If you are using GET (please don't) this should be the first parm. Set it to test=1 to avoid saving any actual data.
- imageURL - This is case sensitive. This can be any reachable image in jpg, gif, png format. You can use ftp, http, https and even data URLs here. So rather than pushing in a separate call, we will pull it.
- fields - This is the JSON formatted array of fields to be updated. Yes, this is actually optional. But without it, we won't update any field data.
- errorsonly=1 - If you add this to the request, any fields that update without error not be returned. If multiple products are updated, any product with no errors in any field will be completely omitted.
- dupesok=1 - If you add this to your request, fields that try to update with duplicate values will be considered good and will return "ok" instead of the normal "duplicate" return value.
- returnval=1 - If you add this to your request, the value is returned along with the status for each field you update. Normally the value is omitted to save on data packet size. May be useful when debugging.
Each entry in the fields array is made up of keys and data. Some keys are required and some are optional depending on the data type being used. These entries mirror the single field update calls used when updating data one field at a time.
Details of the fields entries
- field - required, the name of the field to be updated
- value - required, the new value for this field
- extra_id - optional, Some fields use 2 fields to store the data. One being a numeric value and the second being a descriptor [such as a ounces, gallons, quarts] This extra value must match the list we keep in our database. You can include the text version of this extra information at the end of the "value" field but it still needs to match what we have. You can also split the value into two fields the way we do passing the number in the "value" field and the descriptor as an index id in this "extra_id" field. For more information, see the "get=extra" in the basic overview for the v3 API.
- reason - used only when you want to delete a field. If you use this, you must set the value field to empty string and give a reason in this field. At least 13 characters are required for this reason.
An example of the JSON to update multiple fields for a single product
The order of each field in the array doesn't matter. We will process them in sequence but sequence makes no difference. So you don't have to sort them or place them in any partcular order.
You can actually update multiple products at the same time. To do this, you still need to pass some basic information for the first product in the required fields (see above). But in the fields JSON, you create an array of products, each with a fields sub-array. The product listed in the update field would be ignored for the most part but must still be valid. So it can be hardcoded when using this method as long as it is a vaild EAN code.
An example of the JSON to update multiple fields for multiple products
It doesn't matter if you are updating a single product or multiple products. When the response is returned, the top level status is always going to be code 200 assuming your required fields passed the test. Then you will see an array of products even if you only passed in one to be updated. Each product entry and each field entry will have a status so you will know if individual updates worked or failed. This includes the imageURL you passed.
An example of the JSON returned after an update call
The return results in each img or status field
- ok - The field or image processed without error
- n/a - No image was sent (not for fields)
- duplicate - The data you sent already exists. (not for images)
- Any other value is an error which may include details but may not.
Try our data update wizard tool to generate sample code.
Examples of how to update images
Here are two examples of updating images. These both use a GET that you can test in your browser as soon as you insert your keycode. No other fields are being updated in these two examples. You would normally want to use POST in your code because there can be issues with very long GET requests losing data off the end. But these examples will work properly as GET or POST.
This first example is updating a single product image in simple mode using only form variables (no JSON)
https://eandata.com/feed/?test=1&v=3&keycode=[YOUR-CODE]&update=0025192251344&field=*bulk*&imageURL=https://schworak.com/image/0025192251344-Jaws.jpg
This next example is also updating a single product image, but because it is using JSON, you could pass multiple products in the outer "fields" array. Notice that each inner product block also has a "fields" list when using JSON.
https://eandata.com/feed/?test=1&v=3&keycode=[YOUR-CODE]&update=0025192251344&field=*bulk*&fields=[{%22ean%22:%220025192251344%22,%22imageURL%22:%22https://schworak.com/image/0025192251344-Jaws.jpg%22,%22fields%22:[]}]