Discussion:
[chromium-dev] How to communicate between browser and render
hao liu
2018-11-19 10:08:22 UTC
Permalink
Hi, I'm very new in chromium developing.
I recently encountered a problem
I am going to add an object to my javascript to get a large piece of text.
Initially I was going to use base::CommandLine to load a file path and open
it in render_process_host_impl.cc
But I found that the text was too long, causing the browser to crash when
dispatched to the renderer.
What method should I use to open the file in the renderer or in the Browser
and then send the data to the renderer so that the javascript object I
added can read it?

Thank you
--
--
Chromium Developers mailing list: chromium-***@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-dev
---
You received this message because you are subscribed to the Google Groups "Chromium-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-dev+***@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-dev/6f7bddcd-e687-46bc-8561-281de3ff5b05%40chromium.org.
Daniel Bratell
2018-11-20 11:20:43 UTC
Permalink
The modern way to communicate information between processes is with mojo,
an inter-process/language replacing the old "IPC" methods.

Since I've not really used it myself, I hope this documentation will be
enough to get going:
https://chromium.googlesource.com/chromium/src/+/master/mojo/README.md

/Daniel
Post by hao liu
Hi, I'm very new in chromium developing.
I recently encountered a problem
I am going to add an object to my javascript to get a large piece of text.
Initially I was going to use base::CommandLine to load a file path and
open it in render_process_host_impl.cc
But I found that the text was too long, causing the browser to crash
when dispatched to the renderer.
What method should I use to open the file in the renderer or in the
Browser and then send the data to the renderer so that the javascript
object I added >can read it?
Thank you
http://groups.google.com/a/chromium.org/group/chromium-dev
---You received this message because you are subscribed to the Google
Groups "Chromium-dev" group.
To unsubscribe from this group and stop receiving emails from it, send
To view this discussion on the web visit
https://groups.google.com/a/chromium.org/d/msgid/chromium-dev/6f7bddcd->e687-46bc-8561-281de3ff5b05%40chromium.org.
--
/* Opera Software, Linköping, Sweden: CET (UTC+1) */
--
--
Chromium Developers mailing list: chromium-***@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-dev
---
You received this message because you are subscribed to the Google Groups "Chromium-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-dev+***@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-dev/op.zsry4tz1rbppqq%40cicero2.linkoping.osa.
Erik Chen
2018-11-20 16:05:07 UTC
Permalink
This exact example is covered here:
https://chromium.googlesource.com/chromium/src/+/master/docs/mojo_guide.md
Post by Daniel Bratell
The modern way to communicate information between processes is with mojo,
an inter-process/language replacing the old "IPC" methods.
Since I've not really used it myself, I hope this documentation will be
https://chromium.googlesource.com/chromium/src/+/master/mojo/README.md
/Daniel
Hi, I'm very new in chromium developing.
I recently encountered a problem
I am going to add an object to my javascript to get a large piece of text.
Initially I was going to use base::CommandLine to load a file path and
open it in render_process_host_impl.cc
But I found that the text was too long, causing the browser to crash when
dispatched to the renderer.
What method should I use to open the file in the renderer or in the
Browser and then send the data to the renderer so that the javascript
object I added can read it?
Thank you
--
--
http://groups.google.com/a/chromium.org/group/chromium-dev
---
You received this message because you are subscribed to the Google Groups
"Chromium-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an
To view this discussion on the web visit
https://groups.google.com/a/chromium.org/d/msgid/chromium-dev/6f7bddcd-e687-46bc-8561-281de3ff5b05%40chromium.org
<https://groups.google.com/a/chromium.org/d/msgid/chromium-dev/6f7bddcd-e687-46bc-8561-281de3ff5b05%40chromium.org?utm_medium=email&utm_source=footer>
.
--
/* Opera Software, Linköping, Sweden: CET (UTC+1) */
--
--
http://groups.google.com/a/chromium.org/group/chromium-dev
---
You received this message because you are subscribed to the Google Groups
"Chromium-dev" group.
To view this discussion on the web visit
https://groups.google.com/a/chromium.org/d/msgid/chromium-dev/op.zsry4tz1rbppqq%40cicero2.linkoping.osa
<https://groups.google.com/a/chromium.org/d/msgid/chromium-dev/op.zsry4tz1rbppqq%40cicero2.linkoping.osa?utm_medium=email&utm_source=footer>
.
--
--
Chromium Developers mailing list: chromium-***@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-dev
---
You received this message because you are subscribed to the Google Groups "Chromium-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-dev+***@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-dev/CAEYHnr3rmQK64H_s%3DJNrmS%3DpSHVwDLmNK6bo8A%3DrAa22%3D9XT5g%40mail.gmail.com.
Loading...