Shawn Xie

Greenhorn
+ Follow
since Nov 11, 2002
Cows and Likes
Cows
Total received
0
In last 30 days
0
Total given
0
Likes
Total received
0
Received in last 30 days
0
Total given
0
Given in last 30 days
0
Forums and Threads
Scavenger Hunt
expand Ranch Hand Scavenger Hunt
expand Greenhorn Scavenger Hunt

Recent posts by Shawn Xie

In the article http://developers.sun.com/techtopics/mobility/midp/articles/smartticket1_2/index.html
it says: The Smart Ticket application is available from Sun's Blueprints web site.

However when I followed the link to the Blueprints site I cannot find the Smart Ticket download. After some search I did found an older version (1.1) of it at
http://java.sun.com/j2ee/1.3/download.html#blueprints.

Could someone help me find where to download the latest version of Smart Ticket (2.0 or later) and provide some guides of how to install/run it at the J2EE 1.4 server?

Thanks in advance!

-Shawn
13 years ago
As I understand so far, AJAX is basically a pulling mechanism for updating web pages dynamically. Is it possible to use pushing instead of pulling in AJAX?

Also I have seen some web applications using AJAX to pull the server every 2 seconds. In this case if the server keeps the http connection alive does it mean the user will occupy one connection channel over the whole session?

My other concern of using AJAX is its impact of the scalability and availability on the web server. It seems AJAX will increase much more workload on the server and network as well. Can we discuss this topic deeper?
13 years ago
JSF
The same problem also bothers me a lot and even made me think is JSF friendly to developers. Later on, I found a workaround: make up a unique id for every component. This is not a clean solution, e.g. why I have to care about id for a simple lable? But it seems work.
15 years ago
JSF
Hi,
Is Sun's JSF RI good enough for a production web site? If I do that, are there any risky issues?

Thanks for your opinions in advance.

-SX
15 years ago
Correction to my previous reply:
Entity beans only allow CMT.
I think "the application server handle the
syncrhonization issues and thus taking it out
of the developer and designers hands" only apply to entity beans. Developers only need to specify transaction attributes either through CMT and BMT and let the app server take care of how a same entity beans are accessed by mulitiple users at the same time.
Stateful session beans do not support concurrent acess. Although at first sight, it seems concurrent access to a stateful session bean is impossible because each stateful session bean just serves one client. Remember, however, the client here has broader meaning than a person and it can be a program and this program can be multi-threaded program. The possibility of concurrent acess to a stateful sesion bean is therefore exist and we need some kind of mechanism to prevent it from happening.