tag:blogger.com,1999:blog-2968924507928694867.post8145184058380686586..comments2023-07-27T21:21:13.643+05:30Comments on The Portal Zone: Will OpenSocial replace existing portal standards ?navaneethhttp://www.blogger.com/profile/13353327711519176349noreply@blogger.comBlogger7125tag:blogger.com,1999:blog-2968924507928694867.post-80899051193581995222022-06-08T07:33:34.140+05:302022-06-08T07:33:34.140+05:30Nice poost thanks for sharingNice poost thanks for sharingBrody Chttps://www.brodycollins.com/noreply@blogger.comtag:blogger.com,1999:blog-2968924507928694867.post-21435600336080367892010-04-29T00:21:08.464+05:302010-04-29T00:21:08.464+05:30Intergadget Communication: A more current link on ...Intergadget Communication: A more current link on the inter-gadget communication is here: http://wiki.opensocial.org/index.php?title=Incorporate_Open_Ajax_Hub_as_Pub-Sub_Mechanism_for_OpenSocial_1.next<br /><br />This represents work that is based on the OpenAjax Hub, which provides a secure mechanism to do the eventing. Here's an article that shows how to do this as well: http://Mark Weitzelhttps://www.blogger.com/profile/06032721373605957949noreply@blogger.comtag:blogger.com,1999:blog-2968924507928694867.post-54722672632724562612008-04-19T00:08:00.000+05:302008-04-19T00:08:00.000+05:30Roller,Inter-gadget communication is planned in fu...Roller,<BR/><BR/>Inter-gadget communication is planned in future but not currently available.<BR/><BR/>http://code.google.com/apis/gadgets/docs/pubsub.html<BR/><BR/>Re: security & aggregation, this is achieved by introducing a gadget server which is separate from the Opensocial container. I plan to blog about my understanding of this in my next post.navaneethhttps://www.blogger.com/profile/13353327711519176349noreply@blogger.comtag:blogger.com,1999:blog-2968924507928694867.post-46732717579811764632008-04-18T23:50:00.000+05:302008-04-18T23:50:00.000+05:30Erik,The OpenSocial architecture uses a gadget ser...Erik,<BR/><BR/>The OpenSocial architecture uses a gadget server to proxy the sources to the client. So the gadget sources need to be accessible only to the gadget server. However, I am not sure how this might work in an intranet/extranet scenario.navaneethhttps://www.blogger.com/profile/13353327711519176349noreply@blogger.comtag:blogger.com,1999:blog-2968924507928694867.post-80711320395442560142008-04-18T08:16:00.000+05:302008-04-18T08:16:00.000+05:30I'm not too familiar with OpenSocial, so I have th...I'm not too familiar with OpenSocial, so I have the following questions related to your piece:<BR/><BR/>Can OpenSocial gadgets cooperate with one another similar to the manner of JSR 168 and 286 portlets? i.e. can they share data and work together?<BR/><BR/>If aggregation is done on the client side, how does that affect the security model? Portal Servers decide which users see which pages/Rollerhttps://www.blogger.com/profile/16904666850142252780noreply@blogger.comtag:blogger.com,1999:blog-2968924507928694867.post-42965449137462361772008-04-18T04:16:00.000+05:302008-04-18T04:16:00.000+05:30I think doing the aggregation on the client is an ...I think doing the aggregation on the client is an issue, because one of the sources may not be directly reacheable by the client. For example, let's say a company has a portal in its extranet, which is reacheable from the internet, and a portal on its intranet, which is not reacheable from the internet. Very controlled connections are allowed from the extranet to intranet.<BR/><BR/>In this caseErik Engbrechthttps://www.blogger.com/profile/11174963559600768092noreply@blogger.comtag:blogger.com,1999:blog-2968924507928694867.post-18445961369936033982008-04-18T02:31:00.000+05:302008-04-18T02:31:00.000+05:30YesYesAnonymousnoreply@blogger.com