Re: OSGi Application nested submodule messaging

Assuming the amount of JS to export is not a lot, I also see exporting
JS and exposing it as a very viable alternative as Jen previously
pointed out.

Something else that comes to mind, a lot more involved I must admit is
to use a server-push approach. The header/footer module keeps an open
connection with the backend. The backend receives a notification that
something changed and pushes back to the UI where the header/footer
module makes the appropriate changes. This eliminates the need to
poll.

I think the exported JS exposed via JSNI it's the simplest and
probably one of the cleanest ways to get this done but wanted to throw
this other approach out there.

Best regards,

Alfredo

On Mon, Aug 6, 2012 at 12:37 PM, Joseph Lust <lifeoflust@gmail.com> wrote:
> Thanks Jen's, I'll give the JSNI and postMessage() methods a try.
>
>
> Sincerely,
> Joseph
>
> --
> You received this message because you are subscribed to the Google Groups
> "Google Web Toolkit" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/google-web-toolkit/-/4tNAb73e9P8J.
>
> To post to this group, send email to google-web-toolkit@googlegroups.com.
> To unsubscribe from this group, send email to
> google-web-toolkit+unsubscribe@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/google-web-toolkit?hl=en.



--
Alfredo Quiroga-Villamil

AOL/Yahoo/Gmail/MSN IM: lawwton

--
You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to google-web-toolkit+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.