You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@shindig.apache.org by Dan Lester <da...@danlester.com> on 2008/02/07 17:39:15 UTC
Getting Gadget Info without rendering gadget
Let's say I have a directory of gadgets that users might want to run on
my site, entered only by URL. I want to display more information about
each gadget to the user so they can make a choice about which gadgets
they might want to run - so, I would want to extract information from
the XML such as author name, thumbnail, description.
So far, I have ripped out bits of code from GadgetRenderingServlet.java,
doing most of the same things as the /ifr servlet except for actually
rendering the gadget. This seems to work, and even uses the same cache I
think. But I just thought there must be a better way? If not, is it
worth adding a class to do this?
I've decided to build the whole site in Java so that I can do things
like this. I'm not sure what I'd do if I was using another language for
the rest of my site.
Thanks for any guidance!
Dan
Re: Getting Gadget Info without rendering gadget
Posted by Kevin Brown <et...@google.com>.
On Fri, Feb 15, 2008 at 6:32 AM, Dan Lester <da...@danlester.com> wrote:
>
> Just a thought: rpc should cater for the 'nocache' attribute - either in
> another input field or with query /rpc?nocache=1.
Yes, this will be added. We should probably open JIRA issues for these
things. Right now it can be resolved by making it so that instead of passing
a dummy ProcessingOptions down to GadgetServer, it passes an
HttpProcessingOptions, which will extract nocache params (amongst other
things).
Eventually, I'd like to refactor the JsonRpc stuff to a generic Rpc
interface so that we can support any wire format (JSON, XML, SOAP,
whatever). This is especially important to large organizations using shindig
that already have custom rpc infrastructure.
>
> Otherwise, I get the cached version for the info, then the ifr might
> return a newer version.
>
> Of course, under normal usage without nocache=1 there's no guarantee the
> cache won't expire between these stages. In fact, even with nocache=1,
> the XML could be changed between calls.
>
> Looking at the code, I wondered if query parameters should be passed to
> gadget server when invoked by the rpc servlet, but in tests it certainly
> doesn't work.
>
> Thanks,
>
> Dan
>
>
> -----Original Message-----
> From: Kevin Brown [mailto:etnu@google.com]
> Sent: 11 February 2008 22:09
> To: shindig-dev@incubator.apache.org
> Subject: Re: Getting Gadget Info without rendering gadget
>
>
> That's exactly the intended use for RpcServlet. Great example!
>
> On Feb 11, 2008 2:04 PM, Dan Lester <da...@danlester.com> wrote:
>
> >
> > OK, I'll keep checking out and trying the Rpc again over the next few
> > days. I'm playing around with both Java and PHP at the moment (but
> > both using Java gadget server of course). My initial code to get info
> > over Rpc just used curl in something like:
> >
> >
> > $gadgets_array = array();
> >
> > foreach ($gadgetUrls as $url) {
> > $gadgets_array[] = array( 'url' => $url,
> > 'moduleId' =>
> > count($gadgets_array)+1 );
> > }
> >
> > $req = array(
> > 'context' => array(
> > 'country' => 'US',
> > 'language' => 'en',
> > 'view' => 'default' ),
> > 'gadgets' => $gadgets_array );
> >
> > $rpc = new
> >
> RpcSender('http://localhost:8080/gadgets/rpc'<http://localhost:8080/gadgets/rpc%27>
> <http://localhost:8080/gadg
> ets/rpc%27 <http://localhost:8080/gadgets/rpc%27>>
> > );
> > $info = $rpc->Send($req);
> >
> > class RpcSender {
> >
> > private $addr;
> >
> > function __construct($addr) {
> > $this->addr = $addr;
> > }
> >
> > public function GetAddr() {
> > return $this->addr;
> > }
> >
> > public function Send($req) {
> > // req is an array-object that needs to be JSON-ified
> >
> > $json_req = json_encode($req);
> >
> > $ch = curl_init();
> > curl_setopt($ch, CURLOPT_URL, $this->GetAddr());
> > curl_setopt($ch, CURLOPT_POST, 1);
> > curl_setopt($ch, CURLOPT_POSTFIELDS, $json_req);
> > curl_setopt($ch, CURLOPT_RETURNTRANSFER, 1);
> >
> > $res = curl_exec($ch);
> >
> > if (curl_errno($ch)) {
> > $res = null;
> > // Should handle curl_error($ch);
> > } else {
> > $res = json_decode($res, true);
> > }
> >
> > curl_close($ch);
> >
> > return $res;
> > }
> > }
> >
> >
> >
> > -----Original Message-----
> > From: Kevin Brown [mailto:etnu@google.com]
> > Sent: 11 February 2008 19:58
> > To: Dan Lester
> > Cc: shindig-dev@incubator.apache.org
> > Subject: Re: Getting Gadget Info without rendering gadget
> >
> >
> > On Feb 11, 2008 11:23 AM, Dan Lester <da...@danlester.com> wrote:
> >
> > > Kevin,
> > >
> > > The JsonRpc servlet is a great contribution - I've got it working
> > > from
> >
> > > PHP.
> > >
> > > However, is there any chance it could return all available details
> > > from the spec? That would include thumbnail_url, width, height,
> > > author_email, etc - every attribute on the ModulePrefs tag, I
> > > suppose.
> >
> >
> > Yes, these will be added. Not all of them are currently supported on
> > the GadgetSpec interface. I'll be adding these over the next few days
> > (after submitting the pending headers patch; see SHINDIG-56). I think
> > we'll ultimately wind up supporting the entire extended spec here, not
>
> > just the canonical one.
> >
> >
> > >
> > > You mention that error handling is "kind of rough". I think any
> > > client
> >
> > > can just cater for the idiosyncrasies for now, but one glaring issue
>
> > > is that any one gadget spec not found causes the whole call to break
>
> > > (returns 'Incomplete processing'). That rather ruins your hard work
> > > to
> >
> > > allow multiple gadget specs to be fetched at once.
> >
> >
> > I went ahead and fixed this in SHINDIG-56 as well. I didn't realize it
>
> > was breaking when anything failed, but rather only when something went
>
> > horribly wrong. I'll double check this.
> >
> >
> > >
> > >
> > > SHINDIG-25 is marked as closed which is why I'm bringing it up
> > > rather than just waiting to see if you had anything more in store...
> >
> >
> > I'd like new , individual bugs to be opened for specific issues as
> > they're encountered, which is why I closed SHINDIG-25.
> >
> > I'm glad you appreciate it, though. Thanks for the feedback!
> >
> > ~Kevin
> >
> >
>
>
--
~Kevin
If you received this email by mistake, please delete it, cancel your mail
account, destroy your hard drive, silence any witnesses, and burn down the
building that you're in.
RE: Getting Gadget Info without rendering gadget
Posted by Dan Lester <da...@danlester.com>.
Just a thought: rpc should cater for the 'nocache' attribute - either in
another input field or with query /rpc?nocache=1.
Otherwise, I get the cached version for the info, then the ifr might
return a newer version.
Of course, under normal usage without nocache=1 there's no guarantee the
cache won't expire between these stages. In fact, even with nocache=1,
the XML could be changed between calls.
Looking at the code, I wondered if query parameters should be passed to
gadget server when invoked by the rpc servlet, but in tests it certainly
doesn't work.
Thanks,
Dan
-----Original Message-----
From: Kevin Brown [mailto:etnu@google.com]
Sent: 11 February 2008 22:09
To: shindig-dev@incubator.apache.org
Subject: Re: Getting Gadget Info without rendering gadget
That's exactly the intended use for RpcServlet. Great example!
On Feb 11, 2008 2:04 PM, Dan Lester <da...@danlester.com> wrote:
>
> OK, I'll keep checking out and trying the Rpc again over the next few
> days. I'm playing around with both Java and PHP at the moment (but
> both using Java gadget server of course). My initial code to get info
> over Rpc just used curl in something like:
>
>
> $gadgets_array = array();
>
> foreach ($gadgetUrls as $url) {
> $gadgets_array[] = array( 'url' => $url,
> 'moduleId' =>
> count($gadgets_array)+1 );
> }
>
> $req = array(
> 'context' => array(
> 'country' => 'US',
> 'language' => 'en',
> 'view' => 'default' ),
> 'gadgets' => $gadgets_array );
>
> $rpc = new
>
RpcSender('http://localhost:8080/gadgets/rpc'<http://localhost:8080/gadg
ets/rpc%27>
> );
> $info = $rpc->Send($req);
>
> class RpcSender {
>
> private $addr;
>
> function __construct($addr) {
> $this->addr = $addr;
> }
>
> public function GetAddr() {
> return $this->addr;
> }
>
> public function Send($req) {
> // req is an array-object that needs to be JSON-ified
>
> $json_req = json_encode($req);
>
> $ch = curl_init();
> curl_setopt($ch, CURLOPT_URL, $this->GetAddr());
> curl_setopt($ch, CURLOPT_POST, 1);
> curl_setopt($ch, CURLOPT_POSTFIELDS, $json_req);
> curl_setopt($ch, CURLOPT_RETURNTRANSFER, 1);
>
> $res = curl_exec($ch);
>
> if (curl_errno($ch)) {
> $res = null;
> // Should handle curl_error($ch);
> } else {
> $res = json_decode($res, true);
> }
>
> curl_close($ch);
>
> return $res;
> }
> }
>
>
>
> -----Original Message-----
> From: Kevin Brown [mailto:etnu@google.com]
> Sent: 11 February 2008 19:58
> To: Dan Lester
> Cc: shindig-dev@incubator.apache.org
> Subject: Re: Getting Gadget Info without rendering gadget
>
>
> On Feb 11, 2008 11:23 AM, Dan Lester <da...@danlester.com> wrote:
>
> > Kevin,
> >
> > The JsonRpc servlet is a great contribution - I've got it working
> > from
>
> > PHP.
> >
> > However, is there any chance it could return all available details
> > from the spec? That would include thumbnail_url, width, height,
> > author_email, etc - every attribute on the ModulePrefs tag, I
> > suppose.
>
>
> Yes, these will be added. Not all of them are currently supported on
> the GadgetSpec interface. I'll be adding these over the next few days
> (after submitting the pending headers patch; see SHINDIG-56). I think
> we'll ultimately wind up supporting the entire extended spec here, not
> just the canonical one.
>
>
> >
> > You mention that error handling is "kind of rough". I think any
> > client
>
> > can just cater for the idiosyncrasies for now, but one glaring issue
> > is that any one gadget spec not found causes the whole call to break
> > (returns 'Incomplete processing'). That rather ruins your hard work
> > to
>
> > allow multiple gadget specs to be fetched at once.
>
>
> I went ahead and fixed this in SHINDIG-56 as well. I didn't realize it
> was breaking when anything failed, but rather only when something went
> horribly wrong. I'll double check this.
>
>
> >
> >
> > SHINDIG-25 is marked as closed which is why I'm bringing it up
> > rather than just waiting to see if you had anything more in store...
>
>
> I'd like new , individual bugs to be opened for specific issues as
> they're encountered, which is why I closed SHINDIG-25.
>
> I'm glad you appreciate it, though. Thanks for the feedback!
>
> ~Kevin
>
>
Re: Getting Gadget Info without rendering gadget
Posted by Kevin Brown <et...@google.com>.
That's exactly the intended use for RpcServlet. Great example!
On Feb 11, 2008 2:04 PM, Dan Lester <da...@danlester.com> wrote:
>
> OK, I'll keep checking out and trying the Rpc again over the next few
> days. I'm playing around with both Java and PHP at the moment (but both
> using Java gadget server of course). My initial code to get info over
> Rpc just used curl in something like:
>
>
> $gadgets_array = array();
>
> foreach ($gadgetUrls as $url) {
> $gadgets_array[] = array( 'url' => $url,
> 'moduleId' => count($gadgets_array)+1
> );
> }
>
> $req = array(
> 'context' => array(
> 'country' => 'US',
> 'language' => 'en',
> 'view' => 'default' ),
> 'gadgets' => $gadgets_array );
>
> $rpc = new RpcSender('http://localhost:8080/gadgets/rpc'<http://localhost:8080/gadgets/rpc%27>
> );
> $info = $rpc->Send($req);
>
> class RpcSender {
>
> private $addr;
>
> function __construct($addr) {
> $this->addr = $addr;
> }
>
> public function GetAddr() {
> return $this->addr;
> }
>
> public function Send($req) {
> // req is an array-object that needs to be JSON-ified
>
> $json_req = json_encode($req);
>
> $ch = curl_init();
> curl_setopt($ch, CURLOPT_URL, $this->GetAddr());
> curl_setopt($ch, CURLOPT_POST, 1);
> curl_setopt($ch, CURLOPT_POSTFIELDS, $json_req);
> curl_setopt($ch, CURLOPT_RETURNTRANSFER, 1);
>
> $res = curl_exec($ch);
>
> if (curl_errno($ch)) {
> $res = null;
> // Should handle curl_error($ch);
> } else {
> $res = json_decode($res, true);
> }
>
> curl_close($ch);
>
> return $res;
> }
> }
>
>
>
> -----Original Message-----
> From: Kevin Brown [mailto:etnu@google.com]
> Sent: 11 February 2008 19:58
> To: Dan Lester
> Cc: shindig-dev@incubator.apache.org
> Subject: Re: Getting Gadget Info without rendering gadget
>
>
> On Feb 11, 2008 11:23 AM, Dan Lester <da...@danlester.com> wrote:
>
> > Kevin,
> >
> > The JsonRpc servlet is a great contribution - I've got it working from
>
> > PHP.
> >
> > However, is there any chance it could return all available details
> > from the spec? That would include thumbnail_url, width, height,
> > author_email, etc - every attribute on the ModulePrefs tag, I suppose.
>
>
> Yes, these will be added. Not all of them are currently supported on the
> GadgetSpec interface. I'll be adding these over the next few days (after
> submitting the pending headers patch; see SHINDIG-56). I think we'll
> ultimately wind up supporting the entire extended spec here, not just
> the canonical one.
>
>
> >
> > You mention that error handling is "kind of rough". I think any client
>
> > can just cater for the idiosyncrasies for now, but one glaring issue
> > is that any one gadget spec not found causes the whole call to break
> > (returns 'Incomplete processing'). That rather ruins your hard work to
>
> > allow multiple gadget specs to be fetched at once.
>
>
> I went ahead and fixed this in SHINDIG-56 as well. I didn't realize it
> was breaking when anything failed, but rather only when something went
> horribly wrong. I'll double check this.
>
>
> >
> >
> > SHINDIG-25 is marked as closed which is why I'm bringing it up rather
> > than just waiting to see if you had anything more in store...
>
>
> I'd like new , individual bugs to be opened for specific issues as
> they're encountered, which is why I closed SHINDIG-25.
>
> I'm glad you appreciate it, though. Thanks for the feedback!
>
> ~Kevin
>
>
RE: Getting Gadget Info without rendering gadget
Posted by Dan Lester <da...@danlester.com>.
OK, I'll keep checking out and trying the Rpc again over the next few
days. I'm playing around with both Java and PHP at the moment (but both
using Java gadget server of course). My initial code to get info over
Rpc just used curl in something like:
$gadgets_array = array();
foreach ($gadgetUrls as $url) {
$gadgets_array[] = array( 'url' => $url,
'moduleId' => count($gadgets_array)+1
);
}
$req = array(
'context' => array(
'country' => 'US',
'language' => 'en',
'view' => 'default' ),
'gadgets' => $gadgets_array );
$rpc = new RpcSender('http://localhost:8080/gadgets/rpc');
$info = $rpc->Send($req);
class RpcSender {
private $addr;
function __construct($addr) {
$this->addr = $addr;
}
public function GetAddr() {
return $this->addr;
}
public function Send($req) {
// req is an array-object that needs to be JSON-ified
$json_req = json_encode($req);
$ch = curl_init();
curl_setopt($ch, CURLOPT_URL, $this->GetAddr());
curl_setopt($ch, CURLOPT_POST, 1);
curl_setopt($ch, CURLOPT_POSTFIELDS, $json_req);
curl_setopt($ch, CURLOPT_RETURNTRANSFER, 1);
$res = curl_exec($ch);
if (curl_errno($ch)) {
$res = null;
// Should handle curl_error($ch);
} else {
$res = json_decode($res, true);
}
curl_close($ch);
return $res;
}
}
-----Original Message-----
From: Kevin Brown [mailto:etnu@google.com]
Sent: 11 February 2008 19:58
To: Dan Lester
Cc: shindig-dev@incubator.apache.org
Subject: Re: Getting Gadget Info without rendering gadget
On Feb 11, 2008 11:23 AM, Dan Lester <da...@danlester.com> wrote:
> Kevin,
>
> The JsonRpc servlet is a great contribution - I've got it working from
> PHP.
>
> However, is there any chance it could return all available details
> from the spec? That would include thumbnail_url, width, height,
> author_email, etc - every attribute on the ModulePrefs tag, I suppose.
Yes, these will be added. Not all of them are currently supported on the
GadgetSpec interface. I'll be adding these over the next few days (after
submitting the pending headers patch; see SHINDIG-56). I think we'll
ultimately wind up supporting the entire extended spec here, not just
the canonical one.
>
> You mention that error handling is "kind of rough". I think any client
> can just cater for the idiosyncrasies for now, but one glaring issue
> is that any one gadget spec not found causes the whole call to break
> (returns 'Incomplete processing'). That rather ruins your hard work to
> allow multiple gadget specs to be fetched at once.
I went ahead and fixed this in SHINDIG-56 as well. I didn't realize it
was breaking when anything failed, but rather only when something went
horribly wrong. I'll double check this.
>
>
> SHINDIG-25 is marked as closed which is why I'm bringing it up rather
> than just waiting to see if you had anything more in store...
I'd like new , individual bugs to be opened for specific issues as
they're encountered, which is why I closed SHINDIG-25.
I'm glad you appreciate it, though. Thanks for the feedback!
~Kevin
Re: Getting Gadget Info without rendering gadget
Posted by Kevin Brown <et...@google.com>.
On Feb 11, 2008 11:23 AM, Dan Lester <da...@danlester.com> wrote:
> Kevin,
>
> The JsonRpc servlet is a great contribution - I've got it working from
> PHP.
>
> However, is there any chance it could return all available details from
> the spec? That would include thumbnail_url, width, height, author_email,
> etc - every attribute on the ModulePrefs tag, I suppose.
Yes, these will be added. Not all of them are currently supported on the
GadgetSpec interface. I'll be adding these over the next few days (after
submitting the pending headers patch; see SHINDIG-56). I think we'll
ultimately wind up supporting the entire extended spec here, not just the
canonical one.
>
> You mention that error handling is "kind of rough". I think any client
> can just cater for the idiosyncrasies for now, but one glaring issue is
> that any one gadget spec not found causes the whole call to break
> (returns 'Incomplete processing'). That rather ruins your hard work to
> allow multiple gadget specs to be fetched at once.
I went ahead and fixed this in SHINDIG-56 as well. I didn't realize it was
breaking when anything failed, but rather only when something went horribly
wrong. I'll double check this.
>
>
> SHINDIG-25 is marked as closed which is why I'm bringing it up rather
> than just waiting to see if you had anything more in store...
I'd like new , individual bugs to be opened for specific issues as they're
encountered, which is why I closed SHINDIG-25.
I'm glad you appreciate it, though. Thanks for the feedback!
~Kevin
Re: Getting Gadget Info without rendering gadget
Posted by Akash Xavier <ak...@gmail.com>.
Dan,
Are you working on a php container?
Can u share some details with others on how you implemented it?
On Feb 11, 2008 11:23 AM, Dan Lester <da...@danlester.com> wrote:
> Kevin,
>
> The JsonRpc servlet is a great contribution - I've got it working from
> PHP.
>
> However, is there any chance it could return all available details from
> the spec? That would include thumbnail_url, width, height, author_email,
> etc - every attribute on the ModulePrefs tag, I suppose.
>
> You mention that error handling is "kind of rough". I think any client
> can just cater for the idiosyncrasies for now, but one glaring issue is
> that any one gadget spec not found causes the whole call to break
> (returns 'Incomplete processing'). That rather ruins your hard work to
> allow multiple gadget specs to be fetched at once.
>
> SHINDIG-25 is marked as closed which is why I'm bringing it up rather
> than just waiting to see if you had anything more in store...
>
> Thanks,
>
> Dan
>
>
> -----Original Message-----
> From: Kevin Brown [mailto:etnu@google.com]
> Sent: 08 February 2008 01:58
> To: shindig-dev@incubator.apache.org
> Subject: Re: Getting Gadget Info without rendering gadget
>
>
> Yes, there will most likely just be a new method on GadgetServer (a new
> class would require replicating much of what it does already anyway).
>
> On Feb 7, 2008 5:32 PM, Dan Lester <da...@danlester.com> wrote:
>
> >
> > Excellent - thanks for pointing me to those open issues.
> >
> > I guess your JsonRpc servlet will be wrapping some classes that I can
> > access directly if I'm using Java. Prefer to use your 'official' code
> > than something I've hacked together for my own purposes...
> >
> > Anyway, I'll have a look at your submission when it's ready.
> >
> > Thanks,
> >
> > Dan
> >
> >
> > -----Original Message-----
> > From: Kevin Brown [mailto:etnu@google.com]
> > Sent: 07 February 2008 17:23
> > To: shindig-dev@incubator.apache.org
> > Subject: Re: Getting Gadget Info without rendering gadget
> >
> >
> > I'm working on a JsonRpc servlet that requires this functionality. If
> > you can wait until this weekend, you'll find that I've already got
> > everything that you probably need. See also
> > https://issues.apache.org/jira/browse/SHINDIG-51 and
> > https://issues.apache.org/jira/browse/SHINDIG-25.
> >
> > On Feb 7, 2008 8:39 AM, Dan Lester <da...@danlester.com> wrote:
> >
> > >
> > > Let's say I have a directory of gadgets that users might want to run
>
> > > on my site, entered only by URL. I want to display more information
> > > about each gadget to the user so they can make a choice about which
> > > gadgets they might want to run - so, I would want to extract
> > > information from the XML such as author name, thumbnail,
> > > description.
> > >
> > > So far, I have ripped out bits of code from
> > > GadgetRenderingServlet.java, doing most of the same things as the
> > > /ifr
> >
> > > servlet except for actually rendering the gadget. This seems to
> > > work, and even uses the same cache I think. But I just thought there
>
> > > must be
> >
> > > a better way? If not, is it worth adding a class to do this?
> > >
> > > I've decided to build the whole site in Java so that I can do things
>
> > > like this. I'm not sure what I'd do if I was using another language
> > > for the rest of my site.
> > >
> > > Thanks for any guidance!
> > >
> > > Dan
> > >
> > >
> >
> >
>
>
--
Akash Xavier
akashmanohar@gmail.com
RE: Getting Gadget Info without rendering gadget
Posted by Dan Lester <da...@danlester.com>.
Kevin,
The JsonRpc servlet is a great contribution - I've got it working from
PHP.
However, is there any chance it could return all available details from
the spec? That would include thumbnail_url, width, height, author_email,
etc - every attribute on the ModulePrefs tag, I suppose.
You mention that error handling is "kind of rough". I think any client
can just cater for the idiosyncrasies for now, but one glaring issue is
that any one gadget spec not found causes the whole call to break
(returns 'Incomplete processing'). That rather ruins your hard work to
allow multiple gadget specs to be fetched at once.
SHINDIG-25 is marked as closed which is why I'm bringing it up rather
than just waiting to see if you had anything more in store...
Thanks,
Dan
-----Original Message-----
From: Kevin Brown [mailto:etnu@google.com]
Sent: 08 February 2008 01:58
To: shindig-dev@incubator.apache.org
Subject: Re: Getting Gadget Info without rendering gadget
Yes, there will most likely just be a new method on GadgetServer (a new
class would require replicating much of what it does already anyway).
On Feb 7, 2008 5:32 PM, Dan Lester <da...@danlester.com> wrote:
>
> Excellent - thanks for pointing me to those open issues.
>
> I guess your JsonRpc servlet will be wrapping some classes that I can
> access directly if I'm using Java. Prefer to use your 'official' code
> than something I've hacked together for my own purposes...
>
> Anyway, I'll have a look at your submission when it's ready.
>
> Thanks,
>
> Dan
>
>
> -----Original Message-----
> From: Kevin Brown [mailto:etnu@google.com]
> Sent: 07 February 2008 17:23
> To: shindig-dev@incubator.apache.org
> Subject: Re: Getting Gadget Info without rendering gadget
>
>
> I'm working on a JsonRpc servlet that requires this functionality. If
> you can wait until this weekend, you'll find that I've already got
> everything that you probably need. See also
> https://issues.apache.org/jira/browse/SHINDIG-51 and
> https://issues.apache.org/jira/browse/SHINDIG-25.
>
> On Feb 7, 2008 8:39 AM, Dan Lester <da...@danlester.com> wrote:
>
> >
> > Let's say I have a directory of gadgets that users might want to run
> > on my site, entered only by URL. I want to display more information
> > about each gadget to the user so they can make a choice about which
> > gadgets they might want to run - so, I would want to extract
> > information from the XML such as author name, thumbnail,
> > description.
> >
> > So far, I have ripped out bits of code from
> > GadgetRenderingServlet.java, doing most of the same things as the
> > /ifr
>
> > servlet except for actually rendering the gadget. This seems to
> > work, and even uses the same cache I think. But I just thought there
> > must be
>
> > a better way? If not, is it worth adding a class to do this?
> >
> > I've decided to build the whole site in Java so that I can do things
> > like this. I'm not sure what I'd do if I was using another language
> > for the rest of my site.
> >
> > Thanks for any guidance!
> >
> > Dan
> >
> >
>
>
Re: Getting Gadget Info without rendering gadget
Posted by Kevin Brown <et...@google.com>.
Yes, there will most likely just be a new method on GadgetServer (a new
class would require replicating much of what it does already anyway).
On Feb 7, 2008 5:32 PM, Dan Lester <da...@danlester.com> wrote:
>
> Excellent - thanks for pointing me to those open issues.
>
> I guess your JsonRpc servlet will be wrapping some classes that I can
> access directly if I'm using Java. Prefer to use your 'official' code
> than something I've hacked together for my own purposes...
>
> Anyway, I'll have a look at your submission when it's ready.
>
> Thanks,
>
> Dan
>
>
> -----Original Message-----
> From: Kevin Brown [mailto:etnu@google.com]
> Sent: 07 February 2008 17:23
> To: shindig-dev@incubator.apache.org
> Subject: Re: Getting Gadget Info without rendering gadget
>
>
> I'm working on a JsonRpc servlet that requires this functionality. If
> you can wait until this weekend, you'll find that I've already got
> everything that you probably need. See also
> https://issues.apache.org/jira/browse/SHINDIG-51 and
> https://issues.apache.org/jira/browse/SHINDIG-25.
>
> On Feb 7, 2008 8:39 AM, Dan Lester <da...@danlester.com> wrote:
>
> >
> > Let's say I have a directory of gadgets that users might want to run
> > on my site, entered only by URL. I want to display more information
> > about each gadget to the user so they can make a choice about which
> > gadgets they might want to run - so, I would want to extract
> > information from the XML such as author name, thumbnail, description.
> >
> > So far, I have ripped out bits of code from
> > GadgetRenderingServlet.java, doing most of the same things as the /ifr
>
> > servlet except for actually rendering the gadget. This seems to work,
> > and even uses the same cache I think. But I just thought there must be
>
> > a better way? If not, is it worth adding a class to do this?
> >
> > I've decided to build the whole site in Java so that I can do things
> > like this. I'm not sure what I'd do if I was using another language
> > for the rest of my site.
> >
> > Thanks for any guidance!
> >
> > Dan
> >
> >
>
>
RE: Getting Gadget Info without rendering gadget
Posted by Dan Lester <da...@danlester.com>.
Excellent - thanks for pointing me to those open issues.
I guess your JsonRpc servlet will be wrapping some classes that I can
access directly if I'm using Java. Prefer to use your 'official' code
than something I've hacked together for my own purposes...
Anyway, I'll have a look at your submission when it's ready.
Thanks,
Dan
-----Original Message-----
From: Kevin Brown [mailto:etnu@google.com]
Sent: 07 February 2008 17:23
To: shindig-dev@incubator.apache.org
Subject: Re: Getting Gadget Info without rendering gadget
I'm working on a JsonRpc servlet that requires this functionality. If
you can wait until this weekend, you'll find that I've already got
everything that you probably need. See also
https://issues.apache.org/jira/browse/SHINDIG-51 and
https://issues.apache.org/jira/browse/SHINDIG-25.
On Feb 7, 2008 8:39 AM, Dan Lester <da...@danlester.com> wrote:
>
> Let's say I have a directory of gadgets that users might want to run
> on my site, entered only by URL. I want to display more information
> about each gadget to the user so they can make a choice about which
> gadgets they might want to run - so, I would want to extract
> information from the XML such as author name, thumbnail, description.
>
> So far, I have ripped out bits of code from
> GadgetRenderingServlet.java, doing most of the same things as the /ifr
> servlet except for actually rendering the gadget. This seems to work,
> and even uses the same cache I think. But I just thought there must be
> a better way? If not, is it worth adding a class to do this?
>
> I've decided to build the whole site in Java so that I can do things
> like this. I'm not sure what I'd do if I was using another language
> for the rest of my site.
>
> Thanks for any guidance!
>
> Dan
>
>
Re: Getting Gadget Info without rendering gadget
Posted by Kevin Brown <et...@google.com>.
I'm working on a JsonRpc servlet that requires this functionality. If you
can wait until this weekend, you'll find that I've already got everything
that you probably need. See also
https://issues.apache.org/jira/browse/SHINDIG-51 and
https://issues.apache.org/jira/browse/SHINDIG-25.
On Feb 7, 2008 8:39 AM, Dan Lester <da...@danlester.com> wrote:
>
> Let's say I have a directory of gadgets that users might want to run on
> my site, entered only by URL. I want to display more information about
> each gadget to the user so they can make a choice about which gadgets
> they might want to run - so, I would want to extract information from
> the XML such as author name, thumbnail, description.
>
> So far, I have ripped out bits of code from GadgetRenderingServlet.java,
> doing most of the same things as the /ifr servlet except for actually
> rendering the gadget. This seems to work, and even uses the same cache I
> think. But I just thought there must be a better way? If not, is it
> worth adding a class to do this?
>
> I've decided to build the whole site in Java so that I can do things
> like this. I'm not sure what I'd do if I was using another language for
> the rest of my site.
>
> Thanks for any guidance!
>
> Dan
>
>