Most of the replies have focused on web based, thin clients. The poster is talking about thick clients where the user has a lot more functionality than a typical web page.
He needs answers to questions such as:
- Do I multithread communications between client and server so that the user can still interact with the UI, or do I use a single threaded model where less things can go wrong?
- Do any patterns exist for editing data models via the UI and implementing undo/redo ( * see the Memento design pattern)
- Exception handling: how to manage errors in communication and data and inform the user in an elegant, consistent manner.
I deal with these issues in my current project - they're pretty common on client side applications, but I haven't been able to find any useful sources to help answer them either.
I think you want to buy shares in Ericsson, not Ericson...unless you are also interested in a small company from Wisconsin developing alternative energy from cow dung.
1. Enable international roaming with your US provider, then - as long as there's a GSM provider wherever you are - people can call you as normal. This costs a lot though, average $1.50 per minute and will be billed by your regular provider.
2. Get a new contract with a provider in your new country. You'll get a new sim card for your phone, and your phone must be unlocked for this to work. This is obviously cheaper for usage, but most providers require a 12 month contract.
This phone is triband so you can use it pretty much anywhere.
Yes. SSID's are used to specify which wireless network you want to be a part of.
Re:A PS2 with different games
on
XBox Released
·
· Score: 1
Very true.
Remember all the fantastic games on the SNES that were the brainchild of Shigeru Myamoto? This one guy did a lot to make the SNES as successful as it was, and it wasn't about the processing ability of the console at all..
Java is too diverse to do a survey like this without splitting it up into smaller parts.
Where is the increase happening ? I suspect the vast majority of it is on the enterprise side which people tend not to think about (they think shrinkwrapped and installed on their desktops).
I'm sure we'll also see another massive jump in the next 2 years with more use by developers of J2ME (the micro edition of Java for cellphones and PDA's) being adopted....and your average joe will notice this.
Java on the client side isn't really dead, it's been waiting for a better platform than the desktop pc.
And this method is exactly how the legendary 'Thresh' won practically every Quake tourney he entered...put'em down and keep'em down. Not pretty but effective.
Slashdot Mirror
"doesn't aid humans"
"what use is it to have a connection anywhere"
WHAT PLANET ARE YOU ON?!?!
The T68 is triband...The T68 reception may not be as good as other models, but there's no reason why you'll lose your service if you leave your area.
How about accessing MLS data to run comps on homes on the spot while you're on the road?
Most of the replies have focused on web based, thin clients. The poster is talking about thick clients where the user has a lot more functionality than a typical web page.
He needs answers to questions such as:
- Do I multithread communications between client and server so that the user can still interact with the UI, or do I use a single threaded model where less things can go wrong?
- Do any patterns exist for editing data models via the UI and implementing undo/redo ( * see the Memento design pattern)
- Exception handling: how to manage errors in communication and data and inform the user in an elegant, consistent manner.
I deal with these issues in my current project - they're pretty common on client side applications, but I haven't been able to find any useful sources to help answer them either.
I think you want to buy shares in Ericsson, not Ericson...unless you are also interested in a small company from Wisconsin developing alternative energy from cow dung.
So in other words, the US is behind in technology, just through choice :p
Thanks for clearing that up..I was under the impression that PrePay sim cardswere inseparable from the phones that used them.
:) - My Erricson T28 is only dual band and works in the US and the UK.
To correct you on dual-band phones though
Usually there's two ways:
1. Enable international roaming with your US provider, then - as long as there's a GSM provider wherever you are - people can call you as normal. This costs a lot though, average $1.50 per minute and will be billed by your regular provider.
2. Get a new contract with a provider in your new country. You'll get a new sim card for your phone, and your phone must be unlocked for this to work. This is obviously cheaper for usage, but most providers require a 12 month contract.
This phone is triband so you can use it pretty much anywhere.
Yes. SSID's are used to specify which wireless network you want to be a part of.
Very true.
Remember all the fantastic games on the SNES that were the brainchild of Shigeru Myamoto? This one guy did a lot to make the SNES as successful as it was, and it wasn't about the processing ability of the console at all..
Where is the increase happening ? I suspect the vast majority of it is on the enterprise side which people tend not to think about (they think shrinkwrapped and installed on their desktops).
I'm sure we'll also see another massive jump in the next 2 years with more use by developers of J2ME (the micro edition of Java for cellphones and PDA's) being adopted....and your average joe will notice this. Java on the client side isn't really dead, it's been waiting for a better platform than the desktop pc.
And this method is exactly how the legendary 'Thresh' won practically every Quake tourney he entered...put'em down and keep'em down. Not pretty but effective.