Re: Problems with Entrys

Leaving everything else to the jini pro's, I find the "transporting user interfaces" interesting. I wrote a really simple Entry mechanism to transport a UI description rather than transporting an implementation. The receiver has an interpreter of sorts that generated HTML from the UI description. 

I later wrote a similar UI interpreter in Flex. I did not hook it up to jini, but could have without difficulty. Even if the UI is Swing or SWT, I would consider a similar approach. Particularly UI's are tolerant of interpreter speeds. Look at emacs for gosh sake. The benefits are many.