FileStream: T-SQL vs Win32
One of our teams is building a database (and application) that will use the FileStream feature of SQL 2008 to store documents.  According to the MS best practices for filestream, the Win32 APIs are the preferred way to access FileStream data, vs using T-SQL.  

However, using the Win32 APIs requires using integrated authentication to connect to the database.  This is a concern for the team because they do not want to give users direct access to the database.  They want the application to connect using a SQL username and password.

What are the pros / cons of using Win32 vs T-SQL to access filestream data?  Are there any factors that would make using T-SQL impossible?
FileStream: T-SQL vs Win32
===

One of our teams is building a database (and application) that will use the FileStream feature of SQL 2008 to store documents.  According to the MS best practices for filestream, the Win32 APIs are the preferred way to access FileStream data, vs using T-SQL.  

However, using the Win32 APIs requires using integrated authentication to connect to the database.  This is a concern for the team because they do not want to give users direct access to the database.  They want the application to connect using a SQL username and password.

What are the pros / cons of using Win32 vs T-SQL to access filestream data?  Are there any factors that would make using T-SQL impossible?