Concepts - Revision history

ArneBab at 14:37, 16 November 2007

ArneBab — Fri, 16 Nov 2007 14:37:08 GMT

←Older revision		Revision as of 14:37, 16 November 2007

		+	[[Category:Development]]
	__TOC__		__TOC__
	''This page is dedicated to ideas about possible futures of Phex. Only some of the things in here wil be in Phex someday, but all of them will help to improve Phex, because they help to spawn more and hopefully new ideas. Definitely open for discussion!'' - [[User:ArneBab\|Arne]]		''This page is dedicated to ideas about possible futures of Phex. Only some of the things in here wil be in Phex someday, but all of them will help to improve Phex, because they help to spawn more and hopefully new ideas. Definitely open for discussion!'' - [[User:ArneBab\|Arne]]

ArneBab: /* Licenses */

ArneBab — Thu, 18 Oct 2007 16:01:02 GMT

Licenses

←Older revision		Revision as of 16:01, 18 October 2007

	====Licenses====		====Licenses====

-	Need a generalized format by which known and new licenses can be parsed.	+	Need a generalized format by which known and new licenses can be parsed.
		+
		+	One example is CreativeCommons RDF: [http://wiki.creativecommons.org/UsingMarkup Markup description] - [http://wiki.creativecommons.org/License_Wrappers Wrappers]

	===Data from the network===		===Data from the network===

ArneBab: /* roleplaying program - finding people, finding maps, finding places, finding objects */

ArneBab — Tue, 03 Jul 2007 06:01:57 GMT

roleplaying program - finding people, finding maps, finding places, finding objects

←Older revision		Revision as of 06:01, 3 July 2007

	==Usecases for an API==		==Usecases for an API==

-	===roleplaying program - finding people===	+	===roleplaying program - finding people, finding maps, finding places, finding objects===

	Imagine a roleplaying program which utilizes Phex.		Imagine a roleplaying program which utilizes Phex.

	Then the people connect, and the network did what it was designed for.		Then the people connect, and the network did what it was designed for.

-	This could also be used to find opponents and partnes for any game.	+	This could also be used to find opponents and partnes for any game.
		+
		+	Also it woud be a good playground for a search-program which connects real-life situations and sales (for example using [http://ripplepay.com ripple] for p2p payment), because bugs (which always exist) aren't as severe in an rpg as in hard real-life.

	===Codesnippet-finding===		===Codesnippet-finding===

ArneBab: /* Usecases for an API */

ArneBab — Mon, 02 Jul 2007 22:55:46 GMT

Usecases for an API

←Older revision		Revision as of 22:55, 2 July 2007


	==Usecases for an API==		==Usecases for an API==
		+
		+	===roleplaying program - finding people===
		+
		+	Imagine a roleplaying program which utilizes Phex.
		+
		+	In conventional programs all runs over a central server. People log on and off regularly.
		+
		+	Now I want to find some people who are interested in just going adventuring.
		+
		+	The program now needs to be able to tell the Core to connect and found its own small network (minimum data for this: first IP/gwebcache, network-name).
		+
		+	Then it needs to be able to define some kind of data, which can be searched for.
		+
		+	With this data, people now advertise their interests.
		+
		+	Now the program needs to be able to start a search.
		+
		+	Results could be, for example, people who want to do one-on-one battles, people who want to join a group of adventurers in the search for the dragon scale on the black hills, people who seek for other people who want to join in their quest, new maps, and much more.
		+
		+	Then the people connect, and the network did what it was designed for.
		+
		+	This could also be used to find opponents and partnes for any game.
		+
		+	===Codesnippet-finding===
		+
		+	Another idea would be to create a program which allows developers to annotate their codesnippets and which shares those snippets to the worls, which are licensed under free licenses.
		+
		+	Programmers could then search for snippets by keyword, language, license and author(s).
		+
		+	For this, a code-editor should be able to just call on Phex to connect, tell it what to share (either the files, or directly the data including additional data which need not be files), and fire searches.
		+
		+
		+	===Other applicatios===
		+
		+	* A Job-Portal

ArneBab: /* What does a GUI need from a backend? */

ArneBab — Mon, 02 Jul 2007 22:42:46 GMT

What does a GUI need from a backend?

←Older revision		Revision as of 22:42, 2 July 2007

	* status: started, running, stopped, finished		* status: started, running, stopped, finished
	* progress: 0 ... 1		* progress: 0 ... 1
		+
		+	==Usecases for an API==

ArneBab: /* Basics */

ArneBab — Mon, 02 Jul 2007 22:42:04 GMT

Basics

←Older revision		Revision as of 22:42, 2 July 2007

	* See a list of running searches		* See a list of running searches
	* Get network-status		* Get network-status
		+	* Connect and disconnect
	* See and modify downloads		* See and modify downloads
	* See and modify uploads		* See and modify uploads

ArneBab at 06:49, 5 June 2007

ArneBab — Tue, 05 Jun 2007 06:49:26 GMT

←Older revision		Revision as of 06:49, 5 June 2007

	__TOC__		__TOC__
-	''This page is dedicated to ideas about possible futures of Phex. Only some of the things in here wil be in Phex someday, but all of them will help to improve Phex, because they help to spawn more and ~~hoefully~~ new ideas.'' - [[User:ArneBab\|Arne]]	+	''This page is dedicated to ideas about possible futures of Phex. Only some of the things in here wil be in Phex someday, but all of them will help to improve Phex, because they help to spawn more and hopefully new ideas. Definitely open for discussion!'' - [[User:ArneBab\|Arne]]

	==What does a GUI need from a backend?==		==What does a GUI need from a backend?==

ArneBab: /* Basics */

ArneBab — Tue, 05 Jun 2007 06:49:00 GMT

Basics

←Older revision		Revision as of 06:49, 5 June 2007

	* See and modify uploads		* See and modify uploads
	* Get Statistics		* Get Statistics
-	* Get ID and ~~descriptionof~~ the Core	+	* Get ID and description of the Core

	Some other things which would be nice:		Some other things which would be nice:

ArneBab: /* Basics */

ArneBab — Tue, 05 Jun 2007 06:48:48 GMT

Basics

←Older revision		Revision as of 06:48, 5 June 2007

	Some other things which would be nice:		Some other things which would be nice:

-	* What happened/which new things are avaible since last ~~connectiong~~ between GUI and Core.	+	* What happened/which new things are avaible since last connection between GUI and Core.

	===Searches===		===Searches===

ArneBab: /* What does a GUI need from a backend? */

ArneBab — Tue, 05 Jun 2007 06:48:11 GMT

What does a GUI need from a backend?

←Older revision		Revision as of 06:48, 5 June 2007


	==What does a GUI need from a backend?==		==What does a GUI need from a backend?==
		+
		+	''Done for a general GUI for different possible backends. -[[User:ArneBab\|Arne]]''
		+
		+	===Basics===
		+
		+	It needs to be able to
		+
		+	* Do searches/queries (for example directly magnet based: They can query by keyword ("kt=") and by hash ("xt=urn:sha1") and by both).
		+	* See search results (per query)
		+	* See a list of running searches
		+	* Get network-status
		+	* See and modify downloads
		+	* See and modify uploads
		+	* Get Statistics
		+	* Get ID and descriptionof the Core
		+
		+	Some other things which would be nice:
		+
		+	* What happened/which new things are avaible since last connectiong between GUI and Core.
		+
		+	===Searches===
		+
		+	A search-request needs to be able to contain
		+
		+	* An ID (number)
		+	* a search-type (query, what's new?, browse host, ...)
		+	* A simple text (simple search)
		+	* a reg-exp search (for possible future features)
		+	* An IP for browse-host
		+	* metadata
		+	** name
		+	** artist
		+	** license
		+	** ... arbitrary
		+	* hash
		+	** sha1
		+	** TigerTree
		+	** ... arbitrary as by magnet
		+
		+	Some of this information could be transferred in a magnet:
		+
		+	* name + hash
		+
		+	====Licenses====
		+
		+	Need a generalized format by which known and new licenses can be parsed.
		+
		+	===Data from the network===
		+
		+	Data which the network could deliver:
		+
		+	* Contact:
		+	** address: IP, ...
		+	** ID: name or GUID
		+	** connected: bool
		+	** connect-time-ms:
		+	** online-time-ms: time the client knows that the network-connection is life
		+	** node-type: supernode, leaf, shielding node
		+	*** node-type-name: ultrapeer, leaf, push-proxy
		+	** nice-name: a name, selected by the user.
		+	** region: country
		+	*** city:
		+	** program-info:
		+	*** name:
		+	*** version
		+	*** system:
		+	*** language:
		+	** crowd: tags by which the network could be organized.
		+
		+	* status
		+	** connected: bool (see contact)
		+	** number-of-live-contacts: number of active peer-connections
		+	** connection-quality: not connected, weak, good, great, exceptional, connected (in case no descriptive status can be set)
		+	** connect-time-ms: see contact
		+	** onlince-time-ms: see contact
		+	**firewalled: yes, no, unknown
		+
		+	===Data from Downloads===
		+
		+	* collected-download-speed-KiBps
		+	* number-of-downloads
		+	* number-of-active-downloads
		+
		+	* download (for each)
		+	** file
		+	*** file-name
		+	** size-bytes
		+	** metadata
		+	*** arbitrary
		+	** hash
		+	*** sha1
		+	*** TigerTree
		+	*** ...
		+	** number-of-sources
		+	** number-of-active-sources
		+	** source (for each source)
		+	*** address
		+	*** name (see network: contact)
		+	*** download-speed-KiBps
		+	*** firewalled: yes, no, unknown
		+	** status: active, waiting, inactive, finished
		+	** progress: 0 ... 1
		+	** parts-completed:
		+	*** ordered list from 0 to 1 (''would a list with the KiB be better?''- [[User:ArneBab\|Arne]])
		+	** searching: bool
		+	** local-file: where the file gets saved
		+	** temporary-file: where incomplete version is saved, as string, maybe with "*" as wildcard or using reg-exp to point to multiple files.
		+
		+	===Data from search-results===
		+
		+	same as for a download, but additionally:
		+	* status: started, running, stopped, finished
		+	* progress: 0 ... 1