Feature request: Support Silverlight, WP7 and Metro

[PokerChang]

The silverlight, WP7 and Metro apps only allow asynchronized operations. E.g. HttpWebResponse.GetResponse() needs to be replaced by HttpWebResponse.BeginGetResponse() and EndGetResponse().

It would be a cool to port LoveSeat to asynchronize to support the future of Windows Metro apps.

I am not aware of any existing async C# couch library. If you know any, please also let me know.

Thanks!

[soitgoes]

I agree. However I would like to avoid breaking the existing syntax so I
think we would need to duplicate all the existing libraries with a postfix
of Async.

Do you have any interest in taking this on? My plate is kinda full at the
moment. We were waiting on the appearance of the async flag in .net 4, so
now that 4 is release we can consider using that.

On Fri, Feb 17, 2012 at 1:30 AM, Chang Luo <
[email protected]

wrote:

The silverlight, WP7 and Metro apps only allow synchronized operations.
E.g. HttpWebResponse.GetResponse() needs to be replaced by
HttpWebResponse.BeginGetResponse() and EndGetResponse().

It would be a cool to port LoveSeat to asynchronize to support the future
of Windows Metro apps.

I am not aware of any existing async C# couch library. If you know any,
please also let me know.

Thanks!

---

Reply to this email directly or view it on GitHub:
#27

Martin Murphy
Whiteboard-IT
http://whiteboard-it.com
(205) 910-0720

[willholley]

I've started an async fork. The API is essentially the same except for async / await support. Next step is to make it portable (prob using the portable HttpClient library). At the moment it's .NET 4.5 only but I think it could be backported with the async shims. Code is at https://github.com/willholley/LoveSeat.Async.

[soitgoes]

Great Stuff Will. I was wanting to do this once 4.5 starts getting strong
adoption so I'm thrilled you took it off my plate.

Rather than rename everything to Async. How would you feel about just
doing a 4.5 branch instead so that we and cross merge bug fixes and what
not.

4.5 could be the default and then we could backport bug fixes but twilight
support for the older .Net versions?

Thanks for the help!

On Tue, Apr 23, 2013 at 1:01 AM, Will Holley [email protected]:

I've started an async fork. The API is essentially the same except for
async / await support. Next step is to make it portable (prob using the
portable HttpClient library). At the moment it's .NET 4.5 only but I think
it could be backported with the async shims. Code is at
https://github.com/willholley/LoveSeat.Async.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/27#issuecomment-16840872
.

Martin Murphy
Whiteboard-IT
http://whiteboard-it.com
w: (205) 588-7102

[willholley]

Thanks Martin,

Yes, I'm happy to look at a 4.5 branch, presumably you mean with
async/await support as the default? The reason I renamed all the methods to
Async was because I had half a thought about keeping both APIs side-by-side
but, somewhat predictably, once async is introduced it is pretty
infectious, and maintaining async and sync APIs within the same project is
a fairly big job.

I'll have a play in the next few days and see if I can knock a 4.5 branch
into shape. There are a few minor fixes and API changes which I made that
would probably be useful to backport as well.

Will

On 23 April 2013 14:39, Martin Murphy [email protected] wrote:

Great Stuff Will. I was wanting to do this once 4.5 starts getting strong
adoption so I'm thrilled you took it off my plate.

Rather than rename everything to Async. How would you feel about just
doing a 4.5 branch instead so that we and cross merge bug fixes and what
not.

4.5 could be the default and then we could backport bug fixes but twilight
support for the older .Net versions?

Thanks for the help!

On Tue, Apr 23, 2013 at 1:01 AM, Will Holley [email protected]:

I've started an async fork. The API is essentially the same except for
async / await support. Next step is to make it portable (prob using the
portable HttpClient library). At the moment it's .NET 4.5 only but I
think
it could be backported with the async shims. Code is at
https://github.com/willholley/LoveSeat.Async.

—
Reply to this email directly or view it on GitHub<
https://github.com/soitgoes/LoveSeat/issues/27#issuecomment-16840872>
.

Martin Murphy
Whiteboard-IT
http://whiteboard-it.com
w: (205) 588-7102

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/27#issuecomment-16858322
.