Thats what I was thinking too :S... From first look its exactly the same?

@Anders, you didn't add the "Tea.OEmbed.dll" to your package, so it currently doesn't work!

I agree, this seems exactly like oEmbed macro.  I'm all for a little competition, but does it offer anything different?

Cheers, Lee.

@Lee Thanks for seeing that the dll was missing. I have uploaded a new zip file.

At the moment it looks as almost the same as your package i see. I made a tweet about the project and poul asked me to submit it, so i submitted.

In near future i will make some improvements for the package and try to extend to more providers. Maybe we should put our heads together and migrate our knowledge?

Hi Anders, I'm glad that you have submitted it here! The more the merrier! But if the projects are identical, then maybe some collaboration is needed?

The oEmbed macro project isn't mine, Christian Palm is the developer of that - if you want to get in touch with him, then via his twitter or website is best.

Cheers, Lee.

Thanks to oohembed, it now supports captioned video through dotSub (probably english only, since the language has to be in the embed link.

btw, one difference for me, is that the other cpalm insert, doesn't (at this point) work with the oohembed dotSUB.

http://captionwire.com/samples/dotsub/dotsub-with-insertvideo-plugin.aspx

Hi Bill,

Sounds great with the support for dotSUB in oohEmbed!! I clicked your link but no video is shown at the moment. Is than an error in my code or is the link to dotSub wrong and thats because no video is displayed?

Hi All

After looking at the code (via Reflector) I can see no difference in the two packages. Mine also works with dotSub.

The are both lacking the caching of the response from oohEmbed :-) who will get the caching implemented first (cache key = oohEmbed and duration 10 minutes)

/CPalm

Hi CPalm,

Yes caching is missing :) Would you cache the complete resource or just the result from oohEmbed? ( The image url/flash embed code )

Looking into your code I would

if (!base.IsPostBack && !string.IsNullOrEmpty(this.SourceUrl))
{
    // Some concating of the url
  // ...
    string cacheKey = "OEmbedControl::" + oohEmbedUrl.ToString();
 if (HttpContext.Current.Cache[key] != null)
   {
     this.LitContent.Text = HttpContext.Current.Cache[key];
        return; // Cache used...
  }
 
  // Do the oohembed calls
  // ...
    
  string html = jSerialize.Deserialize<OEmbedResponse>(jsonResponse).GetHtml();
   HttpContext.Current.Cache.Insert(cacheKey, html, null, DateTime.Now.AddMinutes(10), Cache.NoSlidingExpiration);

 this.LitContent.Text = html;
}

Looks like what i had thought out in my head :)

What is the best convention for key naming in Cache? Have your namespace or project name in the key or?

Updated my code to use caching. But how do i upload the new project file without resetting the download counter?

I think I just jumped the gun on saying it was working. I'll have to compare the embed codes. But dotSUB told me they are working on doing their own oembed and should have it this week. Don't know how that effects detection/development.

I kind of agree with the oohembed guy, that it's nice to have just one source...

dotSUB now has official oembed support - http://solutions.dotsub.com/oEmbed

is working on a reply...