Sad that every single one of those is true in lots of shops.
Dr Herbie said:Ray7 said:*snip*
I don't think C9 is a service -- I think it's an experiment. When a new framework is created for web sites, C9 gets used as a testbed for the bits.
Betting 'next C9' is a test for the Orchard framework.
Probably not, but I find it fun that you even thought that.
Used to be in 18, then 24, now 42 (working on http://orchardproject.net). Usually have lunch between 42/43, but sometimes go over to 40/41 or the Commons. I drive past Nintendo every day to get to work. The offices in Bellevue are niiiiice.
ZippyV said:Duncanma said:*snip*
I think the biggest problem is going to be the bandwith. Lately, it's been impossible for me to watch a streaming video from C9 without the constant buffering screen.
Smooth streaming should help with that since it dynamically scales the resolution back if your bandwidth can't handle it. That or just keep downloading the files.
Charles said:HumanCompiler said:*snip*
By reasoning, I'm talking about mapping extensions, which point to some type of execution "engine" (DLL). Just because you can have URL's without any extensions (like.aspx, .whatever,...) doesn't mean that when you supply a URL ending in a "." that IIS will magically understand what this means. At any rate, I'm certain Erik and rest of the C9 dev stars will solve this issue. My vote is to prevent this from happening by not allowing usernames to be created that end with ".". For the ones that currently do (I think there's just one), remove the trailing dot and call it a day (so, change the user name to have no "." at the end, in the db).
Yup, that's the solution we decided on. Not sure if Duncan got around to fixing that yet or not.
Dodo said:HumanCompiler said:*snip*
Probably because filenames must not have a dot at the end, because a dot in the end would indicate you mean a directory instead of a filename with no extension, in the case both are present. I see, so IIS is still evil and unable to pass all URLs to the application...
Yes, evil. It's out to get us.
Dodo said:Charles said:*snip*
Why would you need to reason for an execution path? Just use a default one, for everything.
All URLs under the path of where the application resides should be passed to the application and the application determines which content should be displayed. Does IIS mandate a file extension of some sort? If so, that's bad.
No, IIS does not. Do you see any file extensions in Channel 9 urls?
This seems to just be a weird (more than likely legacy) case.
For the "pause it from advancing" part, you can do that today. Just roll over it. It will pause until you roll off of it.