On Tue, Jul 29, 2008 at 9:55 AM, Brandon Peters
<[EMAIL PROTECTED]> wrote:
> Cassie,
> Thank you for the reply. Just a few more questions:
>
> 1) When you mention 'asking the gadget server' how would I go about
> doing this from the ActivitesService?

You'll need one of the php guys to answer this.

>
> 2) When you mention evaluating an activity on the way out, do you mean
> when I display the activity on my SNS?

yes. or, when you respond to a fetch activities call.

>
> Thanks a lot,
> Brandon
>
> On Mon, Jul 28, 2008 at 8:08 PM, Cassie <[EMAIL PROTECTED]> wrote:
>> Validating the activity would be specific to your SNS. Do you allow
>> activities to be created for just the currently logged in user? Or can a
>> user create an activity for their friends? Do you have a length limit on the
>> title size? etc etc. That's all up to you.
>>
>> As for template expanding - I'm not sure if anyone has this yet. The idea
>> here would prob be to ask the gadgets server for the message bundle
>> corresponding to the titleId and then you would have to expand that template
>> using the activity's templateParams field. You could also evaluate on the
>> way out instead of on the way in so that you can present summaries of
>> activities.
>>
>> I don't think we will have more info than that until someone actually does
>> it...
>> Hope that helps.
>>
>> - Cassie
>>
>>
>> On Mon, Jul 28, 2008 at 9:16 AM, Brandon Peters <[EMAIL PROTECTED]>wrote:
>>
>>> Hello,
>>> I'm working on implementing an ActivitiesService for my SNS and I've
>>> come across this line:
>>>
>>>  // TODO: Validate the activity and do any template expanding
>>>
>>> Any suggestions on how to validate an activity, or do template
>>> expanding. I'm especially interested in template expanding because I
>>> have a gadget I've written that is using it. I've looked around the
>>> Shindig PHP and noticed several references to Substitutions and such,
>>> but wasn't sure how to access any of that from the ActivitiesService
>>> class. Thanks,
>>> Brandon
>>>
>>> --
>>> Brandon Peters
>>>
>>
>
>
>
> --
> Brandon Peters
>

Reply via email to