[Building Sakai] BasicLTI profile pictures

[Adrian Fish]

Hi Steve,

Thought you might reply. Not many people seem to talk about basic lti. It's
the same in Moodle land :)

I really don't like the idea of calling back in via http. It'll be
painfully slow compared to accessing memory and will temporarily use a
connection thread. I've not benchmarked it or anything, but it just seems
inefficient.

Cheers,
Adrian.


On 17 December 2012 12:18, Steve Swinsburg <steve.swinsburg at gmail.com>wrote:

> Could you just use the URL?
>
> /direct/profile/[userid]/image
>
> I actually want to make the tool use those image URLs everywhere so its
> neater and can cut out some code.
>
> If the issue is the entity provider prompts for auth, I say we just open
> it up - privacy settings will still be checked.
>
> cheers,
> Steve
>
>
>
>
> On Mon, Dec 17, 2012 at 10:27 PM, Adrian Fish <adrian.r.fish at gmail.com>wrote:
>
>> Hi all,
>>
>> I'm looking at https://jira.sakaiproject.org/browse/BLTI-155 which
>> covers the acceptance and provisioning of profile pictures from a LTI
>> consumer.
>>
>> The easiest way to do this would be to compile profile2 api calls
>> directly into the blti code although this would mean a coupling between the
>> two projects. An alternative would be to use reflection to test for the
>> availability of the profile2 apis at runtime. Another alternative would be
>> to use the legacy profile api call, setPictureUrl.
>>
>> I'd rather avoid reflection if possible due to the cost. Any ideas
>> anybody?
>>
>> Cheers,
>> Adrian.
>>
>> _______________________________________________
>> sakai-dev mailing list
>> sakai-dev at collab.sakaiproject.org
>> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>>
>> TO UNSUBSCRIBE: send email to
>> sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of
>> "unsubscribe"
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20121217/1783f639/attachment.html