I Might be able to once i get the dough...
I could host one but:
1) I need dough (i will need to buy a 10 gig hd, a cd-rom, and some mem)
2) My server would need a max of about 50 people and it couldn't be taking up tons of bandwith and such, this would only be on 0.2 Meg cable :) along with a hub for direct connect and my name server :)
That's about it so if i get the dough and like i said in #2...
Andy
Something to think about!
...Napster sucks in the fact that the same song is listed & relisted and relisted!
Who decides who is really the originator of code tips?
I've been on sites where you see the same code posted under different names with
"this code is copyrighted by me..you are free to use...."
I've seen some who claim authorship of "Unload All Forms" or other basic VB Functions.
oodles and ooldles of similar code with 200,000,000 self claimed authors....
.....nice thought but it needs thinking!
Yeah, i agree it needs thought...
I agree that the program needs a lot of thought, but I am definately going to try to set this idea up. After monday the 19th June, I am off school for the summer for about 2 1/2 months, so I will be able to really work on the project.
First off, I will develop a code organising app for searching local HD folders and files, browsing files by subject etc...
After this it needs some thought. I agree on the subject of people re-submiting code and calling it their own. How could we get past this? I think that an FTP site that is moderated by a group of us would be the best idea, it would also save a lot of trouble with implementing users on a server, getting clients to connect to the server, then to another client.... yada yada... :)
If you want in on the project, then please post with any expertise that you can offer :D :D :D WildGhost, i take it you're in on the project then? :)
Also, if you don't want in on the project development side of things, then please can you speak out on what type of features you would want in this app? Such as search for, subject areas (API, Network, Beginner) etc. Downloads, articles and tutorials etc.
HeSaidJoe, The project will be a kind of 'moderated' planet source code, so that a group of us can filter out the **** that gets submitted (take not planet source code, you should do this (filter)):) :) :)
Laterz
REM
fallnwrld has a good idea
I like fallnwrld's idea about using university resources. I am not sure how much bandwidth it would suck up, but I am sure it can't be a whole hell of a lot for simple code snippets. The university shouldn't have a problem with that. Especially the big ones. I know that the University of Michigan has all kinds of bandwidth. Each hall of every dorm is equipped with an OC-12. The server could have full speed 100BaseT all the time. There have to be some people here that attend there or somewhere like it. Then we just need to come up with a dedicated server to stick in the corner of someone's dorm room. =)
-CD
Cool! Do it dudes! I have some suggestions you might want to see.
Don't create a napster-like program. I hate Napster!!!! :rolleyes:
I think we should create a program that lets the user connect to a website, download a file (the database), then do offline searches. Of course, the search results will contain the URL to the source code snippet. Then the program will have a function that fires up IE or Netscape upon clicking on the link. From the site itself, the user can view the code. Of course, it would be best if there's a downloadable example of the code snippet.
So far, I am trying to say we create a LiveUpdate-like proggie. (LiveUpdate's from Symantec if you do not know :p)
Hope this suggestion helps! PiKa!
P.S: We can always seek help from VB-World.Net and the 'infamous' Microsoft! :rolleyes:
[Edited by PiKaPrO on 06-07-2000 at 07:35 PM]
I hate to rain on the parade...
Sorry I didn't weigh in earlier, I've been out of town. I
hate to be another one against this project because I would
like to encourage code sharing as well.
BUT, let's look at how Napster works:
When it enocounters a song on your computer, it checks the
database on Napster to see if the song exists. If it does,
then it adds your machine as a possible host for this song.
If the song does not exist, then it is added to the Napster
database with your machine as the only host (thus giving
many multiple entries when titles don't exactly match.)
Now, consider what you're proposing:
You want to share many lines of code, EACH LINE HAVING
INFORMATION THAT COULD BE A POSSIBLE SEARCH KEY. Say for
example you searched for a code snippet on using the
GetDeviceCaps API call. Presumably, you'd want to find
any example which used it, not just ones called
"GetDeviceCaps example" or something similar.
Here's the point:
What you really want to do is a full-text search of the
available code so that the user can not only locate the
string GetDeviceCaps, but can locate it in the proper
context.
So:
If you're going to set up a server which is running a
full-text catalog of all this code on all of our machines,
then it is already housing the full-text of the code! No
need to go look for it on our individual machines to
complete the transaction. (This, of course, is just a
web-based code warehouse).
Still with me?:
Let me make an analogy to Napster, which is where we started
this discussion in the first place. What you're proposing
to do is NOT as similar to Napster as it seems. You're not
just asking "Find a machine with Layla on it"; instead your
asking "Find that cool piano solo in E-flat which is about
two minutes long in a classic rock song". The server could
answer the first one using a catalog. To answer the second,
it would need to have the actual song.
One more thing:
Don't forget, one of the main motivations for the
architecture that Napster used was LEGAL, not technological.
Napster wanted to be sure that music files were not being
passed directly through their servers because that would
clearly be in violation of the artist's copyrights.
If I can help then I'll help, but I think you've got some
serious issues to resolve on this one...
Thanx for listening.
John