Publisher-Centric API

[GoogleCodeExporter]

This issue is to serve as a reference point for the publisher-centric API 
addition proposal.

Original issue reported on code.google.com by jays...@gmail.com on 2 Mar 2011 at 6:09

[GoogleCodeExporter]

Original comment by jays...@gmail.com on 2 Mar 2011 at 6:10

• Added labels: Type-Enhancement
• Removed labels: Type-Defect

[GoogleCodeExporter]

Original comment by jays...@gmail.com on 2 Mar 2011 at 6:36

Attachments:

• [OpenRTB Protocol Work in Progress - Publisher API.docx](https://storage.googleapis.com/google-code-attachments/openrtb/issue-4/comment-2/OpenRTB Protocol Work in Progress - Publisher API.docx)

[GoogleCodeExporter]

Original comment by js...@pulsepoint.com on 21 Mar 2011 at 4:17

[GoogleCodeExporter]

I think it would be better to define object 
"PublisherPreferences.rules.values", as
-List of strings 
-or have multiple "Values" fields for different types  (ValuesString, 
ValuesInteger)

Only reason is that most high speed json parsers expect fields of fixed type 
(string, integer).

Current example:
"values": ["furniture.com", “carbrand.com”]
"values": [1, 2, 9]

Our suggestion -both solutions
using only strings
"values": ["furniture.com", “carbrand.com”]
"values": ["1", "2", "9"]
or using special field for each fieldtype
"valuesString": ["furniture.com", “carbrand.com”]
"valuesInteger": [1, 2, 9]

Original comment by logar.da...@gmail.com on 21 Jun 2011 at 4:09