[Tutor] My Query - How to implement multi threading with remote execution capability in python to achieve parallel processing
alan.gauld at btinternet.com
Tue Dec 23 10:53:36 CET 2014
On 23/12/14 02:58, Alex Kleider wrote:
> On Dec 22, 2014 12:36 PM, wolfrage8765 at gmail.com wrote:
>> On Mon, Dec 22, 2014 at 6:27 AM, Vishwas Pathak <
>> vishwas_pathak at persistent.com> wrote:
>> Your Disclaimer alone means that I can not respond to this question, or
>> else it would apparently become the property of Persistent Systems Ltd. I
>> prefer Open Source to closed source... good day.
I don't see where you get that from?
The disclaimer follows a pretty standard corporate pattern
that simply tries (usually unsuccessfully) to protect
>>> This e-mail may contain privileged and confidential information which is
>>> the property of Persistent Systems Ltd.
It may. It may not. This particular email apparently does not.
Nothing unusual there. It's vague to the point of being useless
but it does not claim ownership of anyone's IP but their own.
>>> It is intended only for the use of the individual or entity to which
>>> it is addressed.
So in this case the mailing list is the entity. But the claim is true of
most emails. We expect them to go to the entity to which we send them.
We may not want them shared publicly or widely.
>>> If you are not the
>>> intended recipient, you are not authorized to read, retain, copy, print,
>>> distribute or use this message.
Again that's pretty general. You are not authorized by the sender to
read the message. It doesn't prevent you from doing so but they aren't
authorizing it and any action an unauthorized viewer takes can therefore
be challenged in court. That's all it means, they have the option of
challenging. It's akin to a copyright statement.
But since the list members are part of the entity addressed it doesn't
apply to us in this case.
>>> If you have received this communication in
>>> error, please notify the sender and delete all copies of this message.
Again a reasonable request since it potentially implies a security issue
for the corporation.
>>> Persistent Systems Ltd. does not accept any liability for virus infected
This is the only bit that is not reasonable. If Persistent Systems sends
a virus infected email out it is there responsibility. If their systems
are infected they are liable.
But I don't see anything too outrageous about the disclaimer. The
corporate banner we used to have was equally banal and said much
the same stuff.
Author of the Learn to Program web site
Follow my photo-blog on Flickr at:
More information about the Tutor