[daisy] [GSoC] applying for the development of a .NET library for Daisy

[Cyberchand]

Marc Portier a écrit :
> I think this proposal should take a change in strategy.
> 
> To be more concrete I think the project should deliver one selected
> application of the suggested Daisy.NET usages (the word plugin, the
> asp.net or whatever custom client) describe what that will do, how it
> will work, and which parts of the Daisy API that will touch upon (thus
> what would be available in the resulting Daisy.NET lib)

Why do you think that the remote API cannot be simply written using a 
WSDL format? May it be possible to imagine functions, running as 
webservices, like GetDocumentVariant(id, branch, ...), or 
MakeQuery("select ... from..."), etc ? I mean, when you developed the 
actual HTTP/XML api, you may had that idea, but for what reasons did you 
choose the actual implementation, instead of a webservices oriented 
interface, which might be more convenient to use? (It is my personal 
opinion though...)

However, as you seem very not convinced by the idea of writing a second 
API (and it is understandable... moreover it is not actually conceivable 
to change the entire api because of the lack of retrocompatibility that 
would follow), I got back to a variant of my first idea, and I changed 
(once again...) my proposal ! I hope it will be the good one :o)

Looking forward feedbacks, as usual...

Cyrille

	

	
		
___________________________________________________________________________ 
Yahoo! Mail réinvente le mail ! Découvrez le nouveau Yahoo! Mail et son interface révolutionnaire.
http://fr.mail.yahoo.com