> I used the WebClient class mostly for convenience but (Http)WebRequest is<br>
> really needed since it allows for a timeout and a redirection limit and a<br>
> limit on the amount of data it's willing to receive.<br>
<br>
Youre right, WebClient is nice but the proper approach is from the
WebRequest standpoint given the nature of the design/purpose of a
WebClient and the short term 'relationship' taking place which is less
of a relationship and more of a simple service being provided.<br>
<br>
> The C# version is more of a hybrid though :). I started it because I<br>
> couldn't really get a decent trace with just PHP on both ends.<br>
<br>
Have you looked at and/or installed Phalanger? Take a look at
<a href="http://www.php-compiler.net">http://www.php-compiler.net</a> and you may find just what the Dr. ordered
if you are more of a PHP guy but want the power of the .NET platform
enough to push your development more towards the <a href="http://ASP.NET">ASP.NET</a> style of
coding. I have found a few projects that have proven a pain in
the butt to try and implement (e.g. Drupal is one I have yet to get
working via Phalanger , IIS, and <a href="http://ASP.NET">ASP.NET</a>) but there are enough BIG PHP
projects out there that run without a hitch and I can verify the speed
increase is absolutely spot on... it really does kick some serious
standard PHP and PHP+Zen a$$.<br>
<br>
Beyond this and moving forward from a complete C# <a href="http://ASP.NET">ASP.NET</a>
implementation standpoint... as I mentioned there are several of us who
have expressed interest in such an implementation and have flirted with
actually moving forward with it several times but have run into similar
concerns in regards to what is the current and (more than likely or at
least very close to) final specification for the first release.
Up until this point I have been looking at the Perl server-side code
base and I know there are several threads that have done a really good
job of summing up the current state quite nicely. None-the-less
the question is definitely worth bringing up again to ensure that what
is developed is based on what these fine architects have been working
over to perfection over the last few weeks (its been a fun process to
watch although I must admit I havent been able to keep up all that well
as of late and as such have definitely been left trying to make sense
of things from the outside looking in and have definitely had a hard
time nailing down exactly what needs to be implemented and the proper
sequence of each process within each algorithm within the start to
finish transaction of a properly implemented OpenID client/server
transactional process.<br>
<br>
To The Group: I hate to ask this question again but to ensure
that we can simply just write the code and know that it is
architecturely correct from the start can someone either point to the
thread or possibly an up-to-date document or wiki entry that contains
the hard core technical specification of OpenID from start to finish
that is either non-language/platform specific (e.g. doesnt focus on the
Perl modules necessary to implement a successful implementation) and
instead each and every step of the process, the name and mandatory
and/or optional parameters, and the expected return type and if
necessary, the actual value of the type if practical/possible.
You are all obviously aware of just how popular this project will
become once a final release is made and word hits the streets. The
potential of .NET installs is enormous and as such having a fully
tested and fully functional implementation ready to go at the release
will go a long ways in bringing in these developers to the OpenID way
of thinking immediatelly.<br>
<br>
I cant remember if I ever announced the location of the Subversion
repository and Trac Project Management interface for the <a href="http://OpenID.NET">OpenID.NET</a>
project we technically started a few weeks ago. In case they are not widely known the Trac UI for this project is at:<br>
<br>
> <a href="http://trac.x2x2x.org/projects/openid.net">http://trac.x2x2x.org/projects/openid.net</a> <br>
<br>
and the Subversion repository is located at:<br>
<br>
> <a href="http://source.x2x2x.org/svn/OpenID.NET/">http://source.x2x2x.org/svn/OpenID.NET/</a> <br>
<br>
Nothing has been checked in as we haven't been able to determine
(completely from our own lack of time to properly manage things) just
what it is we need to develop. I do know that once we get that
nailed down it will only be a matter of a few hours, if that, to get
things developed enough such that the project can begin the testing
phase. As such any and all help will most definitely be
appreciated as I know quite a few projects who are anxious to take the
implementation we create and put it into immediatte use.<br>
<br>
Jason, do you have any thoughts/comments at the moment?<br>
<br>
Thanks everyone!<br>
<br>
<M:D/><br><br><div><span class="gmail_quote">On 6/23/05, <b class="gmail_sendername">meepbear *</b> <<a href="mailto:meepbear@hotmail.com">meepbear@hotmail.com</a>> wrote:
</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">>Hi,<br>><br>>You mentioned a C# version in your original post. Have you opened the
<br>>source<br>>for this portion of your implementation? Several of use have been hacking a<br>>C# implementation here and there but had then decided to hold off until<br>>things had become a bit more finalized in regards to architecture. We were
<br>>going to spend some time this weekend but that didnt work out. If you have<br>>a<br>>working C# implementation this would be wonderful!<br>><br>>Any chance of gainging access to this source?<br>The C# version is more of a hybrid though :). I started it because I
<br>couldn't really get a decent trace with just PHP on both ends.<br>It ended up having consumer/UA and server parts but in the current form it's<br>more of a UI protocol debugging aid then something to really plug in an
<br><a href="http://ASP.NET">ASP.NET</a> page as is.<br><br>My biggest concern though is that since I couldn't find a current spec<br>consumer or server, I implemented both at the same time. I'd really like to<br>test it (or the PHP version for that matter) against something someone else
<br>wrote to make sure I didn't just write something that works but isn't<br>actually compliant with anything else before handing it off to someone else.<br><br>Also, there's a number of things I brushed over just because the protocol is
<br>still in flux ("Unhandled exception" is user friendly enough for me :) ) and<br>some things I did wrong in retrospect.<br>I used the WebClient class mostly for convenience but (Http)WebRequest is<br>really needed since it allows for a timeout and a redirection limit and a
<br>limit on the amount of data it's willing to receive.<br><br><br></blockquote></div><br><br><br>-- <br>M. David Peterson <aka:xmlhacker/><br><a href="http://www.xsltblog.com">http://www.xsltblog.com</a>