The phrase "a publication request" is correct and usable in written English.
It can be used when referring to a formal request for the publication of a document, article, or other written work.
Example: "I submitted a publication request to the journal for my research paper on climate change."
Alternatives: "a request for publication" or "a publishing request."
Upon receiving a resource publication request, the publication engine validates and parses the resource description, and stores the received document in its XML text format in the database.
Upon receiving a resource publication request, the publication engine validates and parses the resource description, and stores the received documents as is in the database.
For each trial, we sent one resource publication request containing a document describing 2 virtual resources.
As for the generated network load, it showed a logarithmic growth pattern with values ranging from 26 KB for 1 publication request to 240 KB for a 1000 publication requests.
If the use of any of the resources in ORDB results to a publication we request that you use the following citation format when referring to ORDB.
As shown in Figure 15, the resources' publication operation shows a polynomial (quadratic) growth pattern in terms of response time, which ranged from 204 ms for 1 publication request to 1 minute and 50 seconds for a 1000 publication requests.
As the number of publication request increased, the response time to process the requests increased in a quadratic fashion, while the network load increased in a logarithmic fashion, when two PIP nodes were used as message generators.
As the number of publication request increased, the response time to process the requests increased in an exponential fashion, while the network load increased in a linear fashion.
On average, it took 204.25 ms to process this publication request, which generated 25.89 Kbytes of network load – values that we consider as reasonable.
On average, it took 245 ms to process this publication request, which generated 31.3 Kbytes of network load – values that we consider as reasonable.
