See this one better: http://en.wikipedia.org/wiki/Web_Services_for_Remote_Portlets
Basically allows code to become an "object" that can be used locally or not. For instance : http://www.google.com/ig I have not idea about how was that implemented but with portlets you can have any of the "widgets" in any machine (think about the weather widget served by some weather-specialized portal) and you just call them and use them. Other way to express it: a standard to make a WWW callable API. DBUS for the WWW. AFAIK it has been implemented in Java and .NET For instance, in the rubyonrails web there is a demo about how use Flickr API to search some photos. With portlets, you'll catch an already done flickr widget and insert it in your page. Calling the API is more powerful (you build the UI yourself, etc.), calling the portlet is much easier (you get a possibly very complex object already done). A www ecosystem of widgets done in rails that can be imported with a few lines ... Rocks! I know the current aim of RoR is not that, so I was wanted to know if it was somewhat in the radar or no. Thank you for RoR! On Jan 24, 12:44 pm, "Rick Olson" <[EMAIL PROTECTED]> wrote: > On Jan 23, 2008 7:41 PM, Lawrence Pit <[EMAIL PROTECTED]> wrote: > > > > > > the portlet standard > > > which standard? ;) > > http://en.wikipedia.org/wiki/Portleti suppose. > > -- > Rick > Olsonhttp://lighthouseapp.comhttp://weblog.techno-weenie.nethttp://mephistoblog.com --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en -~----------~----~----~----~------~----~------~--~---
