Comments for Peter Williams

Comment on Java Daemon by Joao Thomazini Neto

Joao Thomazini Neto — Tue, 17 Jan 2012 22:46:55 +0000

Amazing information. Right on target. Many thanks.

Comment on Mercurial and Perforce by Daniel P.

Daniel P. — Tue, 17 Jan 2012 02:20:46 +0000

Whoops… “p4 changes -m1 …#have” shows you your currently-synced-to-changelist…typo… my bad.

Comment on Mercurial and Perforce by Daniel P.

Daniel P. — Tue, 17 Jan 2012 02:20:13 +0000

“p4 changes -m1 …” shows you your currently sync’d changelist (you could have pending changes in your workspace which are not yet checked-in, which won’t be shown in this command).

“p4 opened …” will show you the files which you have that are currently opened for edit (or needing resolved, been deleted, etc).

If you want to edit files by clearing the read-only attribute and then telling perforce about them later, this is how you can do it:
“p4 diff -se … | p4 -x – edit”

this will get the list of files which are different in your workspace than those checked in, and pipe that list into the perforce edit command, thereby opening them for edit and adding them into your default changelist (without wiping out your changes).

Either way, I still think I like Mercurial better. :)

Comment on Developing software as if quality matters by Cloud Technology and the Advancement in Software Engineering Processes | OpenLogic: The Enterprise Open Source Blog

Mon, 02 Jan 2012 12:02:49 +0000

[...] ports, and reverse proxy configurations to get the most out of each box. Creating a cloud based development process, either for a public cloud (like Amazon or Rackspace) or for an internal enterprise cloud, has been [...]

Comment on Developing software as if quality matters by Peter Williams

Peter Williams — Tue, 27 Dec 2011 16:53:22 +0000

ArrayList, pencil and paper. I tried several tools but they were all too complicated and/or limiting.

Comment on Versioning REST Web Services by Peter Williams

Peter Williams — Tue, 27 Dec 2011 16:46:15 +0000

Michael,
It absolutely applies to the content type of POST and PUT requests. Just as the accept header field of GET requests allows the server to give the client the particular representation it requires, the content-type header field of POST and PUT requests gives the server the information it needs to correctly interpret the data set by the client.

Comment on by Peter Williams

Peter Williams — Tue, 27 Dec 2011 16:40:42 +0000

Mike, It means that you cannot add or change the definition of classes at runtime. (Ie, no monkey patching.) My problem with that is that it precludes almost all meta-programming.

Comment on by Mike Brown

Mike Brown — Tue, 27 Dec 2011 00:50:32 +0000

What does that even mean? That libraries are guaranteed to never be swapped out??

Comment on Versioning REST Web Services by Michael

Michael — Fri, 23 Dec 2011 02:08:13 +0000

You talk about using the ACCEPT header – does the same apply to the Content-type of a POST/PUT? Tha API consists of both input AND output.

Comment on Developing software as if quality matters by ArrayList

ArrayList — Thu, 22 Dec 2011 05:53:40 +0000

Flow diagram is great, which tool have you used to makes that ?