Meta tags:

Headings (most frequently used words):

protocol, buffers, to, why, can, release, the, version, how, do, differ, from, add, new, frequently, asked, questions, general, similar, technologies, contributing, did, you, is, first, what, happened, name, does, google, have, any, patents, on, xml, asn, com, corba, thrift, etc, support, for, language, contribute, patches, features, connect, programs, developer, consoles,

Text of the page (most frequently used words):
the (48), protocol (39), buffers (33), and (24), #google (21), that (17), have (14), for (13), you (13), are (10), type (8), thumb (8), label (8), code (7), down (7), this (7), your (7), #release (7), console (6), like (6), new (6), features (6), from (6), project (6), buffer (6), message (6), was (6), developers (5), but (5), very (5), about (5), would (5), not (5), support (5), they (5), developer (4), many (4), out (4), join (4), way (4), useful (4), discussion (4), group (4), people (4), our (4), own (4), rpc (4), any (4), name (4), version (4), some (4), open (4), all (3), web (3), other (3), see (3), what (3), might (3), find (3), feature (3), should (3), most (3), these (3), additions (3), both (3), can (3), add (3), will (3), happy (3), compiler (3), which (3), though (3), format (3), xml (3), patents (3), use (3), refer (3), been (3), why (3), into (3), frequently (3), asked (3), questions (3), home (3), 한국어 (2), 日本語 (2), русский (2), português (2), brasil (2), français (2), español (2), deutsch (2), bahasa (2), indonesia (2), english (2), sign (2), products (2), cloud (2), platform (2), firebase (2), chrome (2), downloads (2), easy (2), problem (2), too (2), samples (2), content (2), page (2), licensed (2), under (2), its (2), license (2), still (2), let (2), know (2), help (2), library (2), maybe (2), simple (2), added (2), one (2), over (2), years (2), ideas (2), them (2), mess (2), regularly (2), turn (2), yes (2), please (2), libraries (2), with (2), design (2), fact (2), such (2), class (2), part (2), several (2), technologies (2), interchange (2), just (2), could (2), used (2), implementation (2), success (2), how (2), differ (2), com (2), has (2), may (2), does (2), time (2), object (2), early (2), had (2), there (2), tag (2), value (2), were (2), proto1 (2), needed (2), first (2), because (2), source (2), faq (2), reference (2), guides (2), subscribe, newsletter, privacy, terms, android, store, dashboard, cast, sdk, actions, play, api, consoles, student, clubs, accelerators, experts, groups, women, techmakers, programs, youtube, twitter, medium, facebook, blog, connect, latest, releases, github, instructions, file_download, easytounderstand, understand, solvedmyproblem, solved, otherup, missingtheinformationineed, missing, information, need, toocomplicatedtoomanysteps, complicated, steps, outofdate, date, samplescodeissue, issue, otherdown, last, updated, 2020, utc, except, otherwise, noted, details, java, registered, trademark, oracle, affiliates, site, policies, apache, creative, commons, attribution, said, hear, mind, able, want, without, changing, underlying, decide, always, suggestions, cautious, adding, things, thing, learned, lots, interesting, specific, cases, accepted, become, bloated, confusing, picky, when, evaluating, look, widely, hopefully, employees, even, team, members, talk, contribute, patches, encourage, create, generators, runtime, languages, start, independent, freedom, manage, fit, held, back, process, also, link, issues, designed, write, check, available, libprotoc, commandlineinterface, language, contributing, worth, noting, define, remote, procedure, call, easily, indeed, limited, defining, tied, services, think, systems, strengths, weaknesses, relies, internally, vital, component, doesn, mean, ideal, solution, every, evaluate, each, alternative, context, asn, corba, thrift, etc, answer, overview, similar, currently, issued, address, concerns, around, since, lost, meaning, today, usually, term, abstract, sense, serialized, copy, memory, representing, parsed, originates, days, before, generate, classes, called, actually, acted, individual, method, users, pairs, individually, calling, methods, raw, bytes, stored, then, written, once, constructed, addvalue, protocolbuffer, proto2, complete, rewrite, keeps, uses, removed, importantly, cleaned, dependencies, yet, sourced, initial, aka, developed, starting, 2001, evolved, course, sprouting, whenever, someone, willing, work, themselves, anything, created, bit, came, conclusion, feasible, happened, getting, form, fun, thought, outside, provide, public, apis, accept, well, more, efficient, going, convert, end, anyway, practically, everyone, inside, projects, bits, technology, already, found, their, dig, appengine, reasons, did, general, document, answers, question, isn, answered, here, ask, away, save, categorize, based, preferences, stay, organized, collections, forum, wayback, machine, http, archive, org, 20221225051507, https, docs, timestamps, capture, fail, 2023, 2022, 2021, jan, dec, nov, 2012, sep, 2026, captures,

Text of the page (random words):
frequently asked questions protocol buffers google developers 85 captures 31 may 2012 03 sep 2026 nov dec jan 25 2021 2022 2023 success fail about this capture timestamps the wayback machine http web archive org web 20221225051507 https developers google com protocol buffers docs faq protocol buffers english bahasa indonesia deutsch español français português brasil русский 中文 简体 日本語 한국어 sign in home guides reference support protocol buffers home guides reference support faq forum home products protocol buffers support frequently asked questions stay organized with collections save and categorize content based on your preferences this document answers some frequently asked questions about the protocol buffers open source project if you have a question that isn t answered here join the discussion group and ask away general why did you release protocol buffers there are several reasons protocol buffers are used by practically everyone inside google we have many other projects we would like to release as open source that use protocol buffers so to do this we needed to release protocol buffers first in fact bits of the technology have already found their way into the open if you dig into the code for google appengine you might find some of it we would like to provide public apis that accept protocol buffers as well as xml both because it is more efficient and because we re just going to convert that xml to protocol buffers on our end anyway we thought that people outside google might find protocol buffers useful getting protocol buffers into a form we were happy to release was a fun 20 project why is the first release version 2 what happened to version 1 the initial version of protocol buffers aka proto1 was developed in google starting in early 2001 and evolved over the course of many years sprouting new features whenever someone needed them and was willing to do the work themselves like anything created in such a way it was a bit of a mess we came to the conclusion that it would not be feasible to release the code as it was version 2 proto2 is a complete rewrite though it keeps most of the design and uses many of the implementation ideas from proto1 some features have been added some removed most importantly though the code is cleaned up and does not have any dependencies on google libraries that have not yet been open sourced why the name protocol buffers the name originates from the early days of the format before we had the protocol buffer compiler to generate classes for us at the time there was a class called protocolbuffer which actually acted as a buffer for an individual method users would add tag value pairs to this buffer individually by calling methods like addvalue tag value the raw bytes were stored in a buffer which could then be written out once the message had been constructed since that time the buffers part of the name has lost its meaning but it is still the name we use today people usually use the term protocol message to refer to a message in an abstract sense protocol buffer to refer to a serialized copy of a message and protocol message object to refer to an in memory object representing the parsed message does google have any patents on protocol buffers google currently has no issued patents on protocol buffers and we are happy to address any concerns around protocol buffers and patents that people may have similar technologies how do protocol buffers differ from xml see the answer on the overview page how do protocol buffers differ from asn 1 com corba thrift etc we think all of these systems have strengths and weaknesses google relies on protocol buffers internally and they are a vital component of our success but that doesn t mean they are the ideal solution for every problem you should evaluate each alternative in the context of your own project it is worth noting though that several of these technologies define both an interchange format and an rpc remote procedure call protocol protocol buffers are just an interchange format they could easily be used for rpc and indeed they do have limited support for defining rpc services but they are not tied to any one rpc implementation or protocol contributing can i add support for a new language to protocol buffers yes in fact the protocol buffer compiler is designed such that it s easy to write your own compiler check out the commandlineinterface class which is available as part of the libprotoc library we encourage you to create code generators and runtime libraries for new languages you should start your own independent project for this this way you will have the freedom to manage your project as you see fit and will not be held back by our release process please also join the protocol buffers discussion group and let us know about your project we will be happy to link to it and help you out with design issues can i contribute patches to protocol buffers yes please join the protocol buffers discussion group and talk to us about it can i add new features to protocol buffers maybe we always like suggestions but we re very cautious about adding things one thing we ve learned over the years is that lots of people have interesting ideas for new features most of these features are very useful in specific cases but if we accepted all of them protocol buffers would become a bloated confusing mess so we have to be very picky when evaluating new features we look for additions that are very widely useful or very simple or hopefully both we regularly turn down feature additions from google employees we even regularly turn down feature additions from our own team members that said we d still like to hear what you have in mind join the protocol buffers discussion group and let us know we might be able to help you find a way to do what you want without changing the underlying library or maybe we ll decide that your feature is so useful or so simple that it should be added except as otherwise noted the content of this page is licensed under the creative commons attribution 4 0 license and code samples are licensed under the apache 2 0 license for details see the google developers site policies java is a registered trademark of oracle and or its affiliates last updated 2020 06 23 utc type thumb down id missingtheinformationineed label missing the information i need type thumb down id toocomplicatedtoomanysteps label too complicated too many steps type thumb down id outofdate label out of date type thumb down id samplescodeissue label samples code issue type thumb down id otherdown label other type thumb up id easytounderstand label easy to understand type thumb up id solvedmyproblem label solved my problem type thumb up id otherup label other file_download downloads protocol buffers downloads and instructions github the latest protocol buffers code and releases connect blog facebook medium twitter youtube programs women techmakers google developer groups google developers experts accelerators google developer student clubs developer consoles google api console google cloud platform console google play console firebase console actions on google console cast sdk developer console chrome web store dashboard android chrome firebase google cloud platform all products terms privacy sign up for the google developers newsletter subscribe english bahasa indonesia deutsch español français português brasil русский 中文 简体 日本語 한국어