Project Distributor: Introduction to our staggered web service model
So Darren and I have assigned in about a month at present on the Project Distributor website. We are begining to progress to that decisive point where the site is pretty coolheaded, we have plenty of users, we are thinking of operating out of the permissible bandwidth for the demo site, and all sorts of other things that lean to bechance all at erstwhile. At present, there are some problems you can plan yourself out of, and others that you in truth have to hold some money at. Our up-to-the-minutest enhancements can be summarized up in a little list.
- Grease one’s palms a domain name and take up hosting in two places. Project Distributor.com should be up fairly before long to company MarkItUp.ASPXConnection.com
- Have people host their ain versions of the application. And that implies a large source release is in the future. At this juncture risk fragmentation.
- Design out fragmentation with a series of cunning features that will get everyone desire to employ the application at hand.
I’m hither to talk about the last two, since Darren already corrupted some extra hosting for us. The concept will be to free a fairly static version of the application so that groups can host tools, code snippets and other source/binary releases for their teams to partake in. The application is very lightweight and well-heeled to set-up, so it won”t require a bunch of hand holding and configuration to get up and running initially. From our standpoint we resolve a number of issues at this juncture. The most obvious problem is what we separate the Lutz Roeder use case..NET Reflector is the central type of application we’500 love to catch hosted because it makes believe it a bit well-fixed to find oneself, not that Google does a tough job, we’d simply like to get a bunch of tools in one place, with some features for feedback, novel releases, and some nerveless client tools for printing.
