> I just finished a web site where documents are published and articles
> are written.
> I am using SQL Server and each Document ID or Article ID is a GUID.
> I am using ASP.NET MVC 1.0.
> 
> I would like to open a twitter account where I would post the title of
> all documents and articles published on this web site so the users
> could follow it through twitter.
> 
> The problem is that if a document is updated or deleted on the web
> site it should be also on twitter.
> 
> My idea was to send the same Document ID or Article ID when I create
> it in twitter.
> 
> But as far as I know Twitter uses INT as id and I am not even sure if
> I can define ...
> ... Or if it is defined internally will I get the value back?
> 
> Anyway, does anyone knows the best way to create this synchronization?

This application is not going to work well in Twitter as you currently have
it defined, because essentially you are trying to change/delete old entries
to make updates rather than simply making updates. By doing the former
instead of the latter, people won't notice these changes because they are
operating on status IDs that most clients will already have marked as old.
Only your newly added articles will be seen, and this is probably not what
you want. For that matter, you cannot make up arbitrary status IDs as keys.

Twitter is not, as you are trying to use it as, a synchronization sump. You
would be better served to simply make updates saying that article X has been
changed, or article X has been deleted. Much less code, and works more with
how most clients expect Twitter to work. On your article side, you will need
to make sure you notice invalid URLs for deleted articles, and notify the
user accordingly that the article does not exist (I assume you are posting
URLs with your article notifications).

-- 
------------------------------------ personal: http://www.cameronkaiser.com/ --
  Cameron Kaiser * Floodgap Systems * www.floodgap.com * [email protected]
-- I've been walking on clouds/'n flipping off rainbows ... -- Strong Bad #150

Reply via email to