QWERTY

1. Some of the readers know more about the subject, so allow them to contribute
2. Others know less about the subject or may have personal agenda. Let "community" handle them via "moderating system" (I think editors also must play a big role in the moderation till the community is not big enough to be self-regulating)
3. Malicious, obscene content should not be reason for not opening up to readers. Let moderation or editor take care.
4. reader vs advertiser - well if reader make the medium trustworthy, in long run you will have more revenue. besides that allow advertisers to reply to the things.
5. Go "Local" and advertise local
6. Think internet as mainstream medium to grow since all others are being reduced.

• When Client needs to receive remote events (obviously not by polling since that adds burden on server)
• A very complex "windowing" GUI with a lot of local event generation, validation, etc which can be too much for javascript which is an interpreted (thus slower) language. - My interpretation
• If the processing rely too much on the business state/session which contains sensitive data (hence needs to be stored some where safe) and in world of SOA there is no place to save them!! - My interpretation
• Too much pain w.r.t. browser incompatibility and immature frameworks and tool support
• In-house applications do not need them since the customer is on uniform platform.
• Debuggin Javascript on browser is terrible - But faster since no compile step and also firefox has good tools(I think)
  • JSEclipse - Not good Enough
  
  Thoughts!!
  Browser synched with the latest version of java.
  Standard Browser APIs for accessing Web Page DOM + Object Model
  Swing Platform and layout manager compatible with HTML
  That's JavaStart??
  
  
  # posted by Shekhar Jha @ 7:36 PM 0 comments links to this post

• "SOA" - anyhow, anywhere, anytime
• Document Management
• BPM/Workflow
• Virtualization of OS, Storage & VPN, Wireless Network
• Application streaming(??)
• Opensource desktop
• Grid

        send encrypted message 
        send encrypted large key
      ---------||------||-------->
Client                                    Server
(Public Certificate)                       (private key)
large key                                    
      <--------||------||---------
         send user/password encrypted with large key

-----------------------------------------
|Secure|Reliable (new)| Tx      |             |
-------------------------------
|Soap  (Message)                   |   WSDL   |
------------------------------------------
| XML/XSD (data)                                  |
------------------------------------------
| http    (transport)   | TCP |Custom(UDP) |
------------------------------------------