I'd like to see some sort of Wiki integration with email. It would allow me to edit the message. After saving the changes could go to all the recipients and original sender and they could see the updated version.
Reminds me of a storty that I once read. There were "advertising zones" on the sidewalk. If you walked into one of these, you were immediately addicted to the product. It was legal because the zones were well marked.
Together is great if you want to create UML diagrams; it is especially nice for class diagrams. If you aren't going to create many UML diagrams then it doesn't really provide much else.
The problem isn't just security risks, but also
logic bugs in the software. I would want to see
a lot of test plans that show that the software
works as stated before we use it.
Then don't tell perspective employers that you are a generalist. Tell them, "Yes I can do that!". Tell them that you are the greatest. Then, if you get the job work hard to become the greatest.
Re:Why isn't XML-RPC considered bloat?
on
ESR On XML-RPC
·
· Score: 1
Show me an excellent and free CORBA implementation for Perl. Make it super simple to use for my super simple needs of having a Java client use my Perl based server. Now, make it easy to run the connection over SSL.
Now I also need to call this perl stuff from an ASP based page using Visual Basic.
This is what is nice about XML-RPC. It isn't the most efficient transport, but you don't always need the baggage that other protocols have.
Developers should never include sensitve info in a cookie (although I don't care much about my slashdot id/password). If you have to I'd suggest encrypting it.
An interesting BBS type of forum that is popping up are Wiki sites.
Wiki sites are really just editable web pages. Somebody starts a page on some topic and then others add to it. You can go in and change what you said a week ago or add something new.
They can be quite nice as the 'editing' feature allows authors to refine what they said eariler.
Slashdot Mirror
Read The Full Privacy Policy
It won't defeat piracy. However, they might get some people who currently pirate to buy the online version.
I'd like to see some sort of Wiki integration with email. It would allow me to edit the message. After saving the changes could go to all the recipients and original sender and they could see the updated version.
6 to 8 weeks ago ... it seemed like forever :)
Reminds me of a storty that I once read. There were "advertising zones" on the sidewalk. If you walked into one of these, you were immediately addicted to the product. It was legal because the zones were well marked.
The screen seems to be as big as my 17" monitor. Also, the price is pretty competitive if you try and compare to PCs.
Together is great if you want to create UML diagrams; it is especially nice for class diagrams. If you aren't going to create many UML diagrams then it doesn't really provide much else.
The problem isn't just security risks, but also
logic bugs in the software. I would want to see
a lot of test plans that show that the software
works as stated before we use it.
Then don't tell perspective employers that you are a generalist. Tell them, "Yes I can do that!". Tell them that you are the greatest. Then, if you get the job work hard to become the greatest.
Show me an excellent and free CORBA implementation for Perl. Make it super simple to use for my super simple needs of having a Java client use my Perl based server. Now, make it easy to run the connection over SSL.
Now I also need to call this perl stuff from an ASP based page using Visual Basic.
This is what is nice about XML-RPC. It isn't the most efficient transport, but you don't always need the baggage that other protocols have.
Actually, there is something that's pretty good. Smalltalk. VisualWorks (by ParcPlace) supports MacOS, Windows, Linux, Solaris and HP.
VisualWorks has a RAD environment, database access (an OO-Relational framework).
It's been around for years and is very mature.
The downside, of course, is that you need to know and be willing to support Smalltalk.
Developers should never include sensitve info in
a cookie (although I don't care much about my slashdot id/password). If you have to I'd suggest
encrypting it.
Wiki sites are really just editable web pages. Somebody starts a page on some topic and then others add to it. You can go in and change what you said a week ago or add something new.
They can be quite nice as the 'editing' feature allows authors to refine what they said eariler.