Talk:Walnut/Secure Distributed Computing - Revision history

Kevin Reid: Reverted edits by 79.164.138.196 (Talk); changed back to last version by Kevin Reid

Kevin Reid — Wed, 26 Jan 2011 14:02:06 GMT

Reverted edits by 79.164.138.196 (Talk); changed back to last version by Kevin Reid

New page

==Proof of Purchase==

I found the explanation puzzling at first, because it mixes two separate issues: security and convenience. I suggest the following alternate end for the section. [[User:NowhereMan|NowhereMan]] 21:37, 29 March 2008 (CDT)

Since we have a convenient trusted third party available that already had authority over all the panels anyway (the javax.swing.Component class object), we can use the "proof of purchase" pattern instead. We could define a globally available transferFocus function accepting two arguments:

* the panel that contains the focus
* the target panel that should receive the focus

With this function, the target panel would not need to receive excess authority anymore to be able to get the focus.

For practicality, we provided a Component.transferFocus method that, instead of the panel containing the focus, accepts as its first argument a list of panels that the client believes to contain, somewhere in their subpanel hierarchies, the focus. In the common case where a whole window lies inside a single trust realm, the client can simply present a reference to the whole window and be confident that the focus will be transferred.

The interesting thing about Component.transferFocus is that the recipient does not actually need the client's authority to reach the component that already has the focus. The Component class already has that authority. The client must send the authority merely to prove he has it, too.

79.164.138.196: mobile tv pdf

79.164.138.196 — Tue, 25 Jan 2011 19:16:32 GMT

mobile tv pdf

←Older revision		Revision as of 19:16, 25 January 2011
Line 15:		Line 15:

	The interesting thing about Component.transferFocus is that the recipient does not actually need the client's authority to reach the component that already has the focus. The Component class already has that authority. The client must send the authority merely to prove he has it, too.		The interesting thing about Component.transferFocus is that the recipient does not actually need the client's authority to reach the component that already has the focus. The Component class already has that authority. The client must send the authority merely to prove he has it, too.
		+
		+	== mobile tv pdf ==
		+
		+	Hi, I'm a newbie here, but I already want to bring all the benefits of me :) So, I want to share my experience with you..
		+	9 days ago, accidentally, i had found the Mobile Phone TV...and I was so delighted with this application
		+	that I decided to talk to you :)
		+
		+	I consider myself a bit of a road warrior. I am on and off jets and through airports at least twice,
		+	usually 4 times a week. I can catch up on news, watch a Discovery program, check up on the stock market or just find something interesting.
		+	The live guide works like cable at home and the connection speed is very good. All in ALL - I RATE A 5 Star program!
		+
		+	but I do not want to leave any links here, so you can email me fairyalexiss@gmail.com
		+	and i will give you the site of this unusual program :)
		+
		+	(but please don't PM me, because it's so difficult to communicate in such kind of way)
		+
		+	so, I hope I was helpful to you)) see you in next posts ..
		+
		+	sincerely
		+	your Alexis....
		+
		+	p.s. English is not my native language, so sorry for any mistakes :)

Kevin Reid: Reverted edits by 87.110.46.92 (Talk); changed back to last version by Kevin Reid

Kevin Reid — Sun, 14 Mar 2010 10:50:05 GMT

Reverted edits by 87.110.46.92 (Talk); changed back to last version by Kevin Reid

←Older revision		Revision as of 10:50, 14 March 2010
Line 15:		Line 15:

	The interesting thing about Component.transferFocus is that the recipient does not actually need the client's authority to reach the component that already has the focus. The Component class already has that authority. The client must send the authority merely to prove he has it, too.		The interesting thing about Component.transferFocus is that the recipient does not actually need the client's authority to reach the component that already has the focus. The Component class already has that authority. The client must send the authority merely to prove he has it, too.
-
-	~~== Quick response ==~~
-
-	~~Very shorts, simple and easy to understand, bet some more comments from your side would be great~~

87.110.46.92: Quick response

87.110.46.92 — Sat, 13 Mar 2010 20:08:55 GMT

Quick response

←Older revision		Revision as of 20:08, 13 March 2010
Line 15:		Line 15:

	The interesting thing about Component.transferFocus is that the recipient does not actually need the client's authority to reach the component that already has the focus. The Component class already has that authority. The client must send the authority merely to prove he has it, too.		The interesting thing about Component.transferFocus is that the recipient does not actually need the client's authority to reach the component that already has the focus. The Component class already has that authority. The client must send the authority merely to prove he has it, too.
		+
		+	== Quick response ==
		+
		+	Very shorts, simple and easy to understand, bet some more comments from your side would be great

Kevin Reid: Reverted edits by 87.110.46.92 (Talk); changed back to last version by NowhereMan

Kevin Reid — Thu, 11 Mar 2010 11:53:13 GMT

Reverted edits by 87.110.46.92 (Talk); changed back to last version by NowhereMan

←Older revision		Revision as of 11:53, 11 March 2010
Line 15:		Line 15:

	The interesting thing about Component.transferFocus is that the recipient does not actually need the client's authority to reach the component that already has the focus. The Component class already has that authority. The client must send the authority merely to prove he has it, too.		The interesting thing about Component.transferFocus is that the recipient does not actually need the client's authority to reach the component that already has the focus. The Component class already has that authority. The client must send the authority merely to prove he has it, too.
-
-	~~== Hi, Everyone! ==~~
-
-	~~I really like when people are expressing their opinion and thought. So I like the way you are writing~~

87.110.46.92: Hi, Everyone!

87.110.46.92 — Thu, 11 Mar 2010 03:57:02 GMT

Hi, Everyone!

←Older revision		Revision as of 03:57, 11 March 2010
Line 15:		Line 15:

	The interesting thing about Component.transferFocus is that the recipient does not actually need the client's authority to reach the component that already has the focus. The Component class already has that authority. The client must send the authority merely to prove he has it, too.		The interesting thing about Component.transferFocus is that the recipient does not actually need the client's authority to reach the component that already has the focus. The Component class already has that authority. The client must send the authority merely to prove he has it, too.
		+
		+	== Hi, Everyone! ==
		+
		+	I really like when people are expressing their opinion and thought. So I like the way you are writing

NowhereMan: Suggested alternate wording for Proof of Purchase

NowhereMan — Sun, 30 Mar 2008 02:37:52 GMT

Suggested alternate wording for Proof of Purchase

←Older revision

Revision as of 02:37, 30 March 2008