[sakai2-tcc] URL Shortening service for Sakai

Steve Swinsburg steve.swinsburg at gmail.com
Tue Sep 21 15:57:41 PDT 2010


I'm not sure where we are with this.

So to rehash:

There is a URL shortening system here:
https://source.sakaiproject.org/contrib/shortenedurl/trunk/

It ships with a No-op, Randomised and bit.ly url shortening implementations. The no-op is default and returns the URL as is. Institutions can configure which implementation they want to use by a setting in sakai.properties, eg:
shortenedurl.implementation=org.sakaiproject.shortenedurl.api.RandomisedUrlService

If people need to add new implementations, they can easily be done by implementing a very simple three method interface:
https://source.sakaiproject.org/contrib/shortenedurl/trunk/api/src/java/org/sakaiproject/shortenedurl/api/ShortenedUrlService.java

The system also has a servlet which handles the randomised URL translation back to the original, and I plan on adding a simple EntityProvider to allow the generation of shortened URLs asynchronously (already done in another project). 

Because of the several parts to it, I am hesitant at this stage about splitting the system up into parts that go into the kernel, and the rest (servlet/entityprovider). 

It is already on an indie release so can be dropped into the build.

I still have some work to do on it (entityproviders, test cases, db stuff) but was holding off to see if it was worthwhile time spent. 

Tools could then start adding fields that show a short url. As mentioned earlier, the default is a no-op so it will do nothing. But I can imagine a short URL being added to the Edit Details page of Resources being pretty a cool starting point. And the wiki. Possibilities are endless and benefits vast!

cheers,
Steve


On 17/09/2010, at 1:37 AM, csev wrote:

> I would gently suggest inclusion rather than exclusion on this one even if we have some confidence issues that lead us to shut it off by default towards the end of QA.
> 
> It might be nice to be able to *assume* this for some of the 2.9 development.
> 
> I am pretty sure that this is simple enough that there will be sufficient resources to maintain this effectively.
> 
> /Chuck
> 
> On Sep 16, 2010, at 11:28 AM, Seth Theriault wrote:
> 
>> Steve Swinsburg wrote:
>> 
>>> As you've discovered, it's got a few modules (API, Impl and a
>>> servlet to resolve the links that the randomised url generator
>>> makes) and I already have it setup as an indie with a Tomcat
>>> overlay so as soon as I can publish an artifact it could be
>>> put into the experimental pom.
>> 
>> So, are we content to leave this (very cool) service alone for
>> 2.8 and encourage people to use it to gain prod experience for
>> possible future inclusion?
>> 
>> Seth
> 
> _______________________________________________
> sakai2-tcc mailing list
> sakai2-tcc at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/sakai2-tcc

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai2-tcc/attachments/20100922/dbb52b17/attachment.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 3689 bytes
Desc: not available
Url : http://collab.sakaiproject.org/pipermail/sakai2-tcc/attachments/20100922/dbb52b17/attachment.bin 


More information about the sakai2-tcc mailing list