i always though ajax was the kind of magic where you provide a callback and then the server sends it all kinds of interesting information, which the client uses all kinds of magic on to provide the information to the user. apparently i was most wrong, as it seems that the format is always the client making a request and the server making one single response to this.. so no pushing data from the server? seems so.. but maybe i need to look at it more later. at least wicket seems to only provide a timed component to make these request on given time intervals. or im just blind and cant find other options. found some similar info on other web pages so.. maybe i will be wiser someday but for now i stick with this belief.
todays attention span goes to having a look at that hype word ajax. so i wanted to try that out. my first geeking goal for this is to build a simple service that provides information on processed items from the server to the client (browser). and to make these updates in ajax style so as soon as an item is processed, the information is shown to the client.. whee
so since i dont like these options and seems i need to use some custom framework communication anyways, i look at a bunch of other frameworks. it all seems very difficult to choose anything with too many options.. since my target example is not that heavy on the client side, i decide to try wicket. i have been watching it for some time as well thinking it might be nice as people seem to like it. so ooh i decide to try that..