Feature Request: Tcp/Ip connection
Moderator: SourceGear
Feature Request: Tcp/Ip connection
Will there ever be an option to use a straight Tcp/Ip connection instead of Http?
Ah -- now I see.Anonymous wrote:Removing IIS.
I can say we've talked a lot about an idea we call a "traditional server". Instead of IIS and ASP.NET, we would just write a good old fashioned "NT Service" which sits around and listens on a socket and serves stuff to the client. SourceOffSite works this way. It's tempting.
But it's a huge change for the product, and for some customers it might be a step backward.
No promises. This change is probably not likely to ever happen. But we definitely see appeal in it.
Eric Sink
Software Craftsman
SourceGear
Software Craftsman
SourceGear
I would say why?
IIS and ASP.net is a very stable application server with a very stable widely supported protocol (http) why re-invent the wheel with your own service and protcol?
One of the draws for us to Vault was that it used SQL and IIS instead of a proprietary repository and proprietary app server and protocol.
Justin
IIS and ASP.net is a very stable application server with a very stable widely supported protocol (http) why re-invent the wheel with your own service and protcol?
One of the draws for us to Vault was that it used SQL and IIS instead of a proprietary repository and proprietary app server and protocol.
Justin
Last edited by Justin on Fri Nov 12, 2004 4:28 pm, edited 1 time in total.
Believe me, we understand this. In fact, we intended this.Justin wrote:One of the draws for us to Vault was that it used SQL and IIS instead of a proprietary repository and propreitary app server and protocol.
But these technology choices are a two-sided coin. We gained benefits like the ones you describe, but we also gained disadvantages.
We don't plan to change anything, but we get tempted sometime when we think about the benefits on the other side of the coin.
Eric Sink
Software Craftsman
SourceGear
Software Craftsman
SourceGear