I like servers. :) I don't know enough .NET to write one from scratch, but
could take a stab at modifying an existing one. I do have some stuff to sort
out before I can contribute any more code though (we have new contracts at
work, all a bit scary and legal and stuff), and am not too sure whether
1) ASP.NET , not ASP … each to be beasts, but different enough to make the
point.
2) When I use the term server, I mean the thing that serves things. Web
servers are often thought of as servers. Really, I swear.
3) The server I speak of is a package server. While CoApp allows you
ASP is a server-side language, yes. Not a language in which one would write
a server. To me, a server is a long-running process which deals directly
with network clients, not a bunch of code for dynamically generating content
on top of an existing web server.
Of course, I could be wrong about AS
On Fri, Feb 11, 2011 at 12:42 AM, Philip Allison
wrote:
> You use the word server, but then mention ASP and Orchard (which I hadn't
> heard of, but appears to be a CMS framework). I am confused. What nature
> of beastie are we talking about here?
ASP is a server-side language, what's the confus
You use the word server, but then mention ASP and Orchard (which I hadn't
heard of, but appears to be a CMS framework). I am confused. What nature
of beastie are we talking about here?
Regards,
Phil
___
Mailing list: https://launchpad.net/~coapp-develo
I mentioned this before, but buried in a status email.
I'm wondering if I could find a couple of volunteers to work on adapting the
NuGet Package server (written in C#/ASP.NET on top of Orchard, uses OData) to
provide us with an awesome live package server. I'd like to get this running
by the
6 matches
Mail list logo
