Re: [Web-SIG] [RFC] Introducing the Emerging-Like Web Applications Protocol 1.0

[Etienne Robillard]

Hi Ian,

Thanks for spotting this to my attention. I've sent a reply
also but it too went blocked, so what have appeared on web-sig
is mostly incomplete.

Here's the relevant links again for your convenience:

http://gthc.org/blog/agile-development/introducing-emerging-like-web-applications-protocol/
http://gthc.org/WebApplicationDevelopment/EmergingLikeWebApplications

Kind regards,

Etienne

Ian Bicking wrote:
> FYI, your post went through to web-sig but without the links...?
> 
> On Wed, Oct 21, 2009 at 7:09 AM, Etienne Robillard
>  wrote:
> Hi,
> 
> Here's a link to a blog entry I've posted about the "Emerging-Like Web
> Applications Protocol 1.0". I've completed written the initial revision
> and wanted to pass it along to the pros.
> 
> Since the development of WSGI specifications seems a little slowed, I
> hope this may helps developers to think in new ways to see development
> of web frameworks in Python and WSGI. ;-)
> 
> Also, this made me think that refactoring WSGI in much smaller parts or
> modules could be helpful and less of a burden than a single document
> with multiple versioning...
> 
> What do you think, can creating a modular specification for WSGI helps
> in nailing down new directions for Python web development ?
> 
> Kind regards,
> 
> Etienne
> 
> http://gthc.org/blog/agile-development/introducing-emerging-like-web-applications-protocol/
> 
> P.S - I tried to send it over to web-...@python.org. But my e-mail
> address is being blocked as spam.  Why is that so ? Why are we putting
> blockers on legitimate recipients ? I thought web-...@python was an open
> list, but apparently only a relatively short list of persons seems to
> have the priviledge of free speech on that forum. This is somewhat a
> frustrating, and IMO is a long standing problem with this Python community.
> 
> This report relates to a message you sent with the following header fields:
> 
>  Message-id: <4adeeb31.9000...@gmail.com>
>  Date: Wed, 21 Oct 2009 07:06:25 -0400
>  From: Etienne Robillard 
>  To: notmm-disc...@googlegroups.com
>  Subject: Introducing the Emerging-Like Web Applications Protocol 1.0
> 
> Your message cannot be delivered to the following recipients:
> 
>  Recipient address: web-sig@python.org
>  Reason: Rejection greeting returned by server.
>  Diagnostic code: smtp;220-mail.python.org ESMTP Postfix 5.7.1 Blocked
> by DNSBL
>  Remote system: dns;mail.python.org
> (TCP|10.23.32.55|50078|82.94.164.166|25) (mail.python.org ESMTP Postfix)
> 
>>

-- 
Etienne Robillard 
Green Tea Hackers Club 
Blog: 
PGP Fingerprint: 178A BF04 23F0 2BF5 535D  4A57 FD53 FD31 98DC 4E57
___
Web-SIG mailing list
Web-SIG@python.org
Web SIG: http://www.python.org/sigs/web-sig
Unsubscribe: 
http://mail.python.org/mailman/options/web-sig/archive%40mail-archive.com

[Web-SIG] (no subject)

[web-sig-bounces+archive=mail-archive . com]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi,

Here's a link to a blog entry I've posted about the "Emerging-Like Web
Applications Protocol 1.0". I've completed written the initial revision
and wanted to pass it along to the pros.

Since the development of WSGI specifications seems a little slowed, I
hope this may helps developers to think in new ways to see development
of web frameworks in Python and WSGI. ;-)

Also, this made me think that refactoring WSGI in much smaller parts or
modules could be helpful and less of a burden than a single document
with multiple versioning...

What do you think, can creating a modular specification for WSGI helps
in nailing down new directions for Python web development ?

Kind regards,

Etienne


- --
Etienne Robillard 
Green Tea Hackers Club 
Blog: 
PGP Fingerprint: 178A BF04 23F0 2BF5 535D  4A57 FD53 FD31 98DC 4E57
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkre6zEACgkQ/VP9MZjcTldwwwCeI5kVxUzAqRV13PzoaFfCHVsE
wRwAoMz8jPJbqqscIb+izg5RbkNBsMVW
=61oR
-END PGP SIGNATURE-
___
Web-SIG mailing list
Web-SIG@python.org
Web SIG: http://www.python.org/sigs/web-sig
Unsubscribe: 
http://mail.python.org/mailman/options/web-sig/archive%40mail-archive.com

[Web-SIG] (no subject)

[web-sig-bounces+archive=mail-archive . com]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi,

Here's a link to a blog entry I've posted about the "Emerging-Like Web
Applications Protocol 1.0". I've completed written the initial revision
and wanted to pass it along to the pros.

Since the development of WSGI specifications seems a little slowed, I
hope this may helps developers to think in new ways to see development
of web frameworks in Python and WSGI. ;-)

Also, this made me think that refactoring WSGI in much smaller parts or
modules could be helpful and less of a burden than a single document
with multiple versioning...

What do you think, can creating a modular specification for WSGI helps
in nailing down new directions for Python web development ?

Kind regards,

Etienne


- --
Etienne Robillard 
Green Tea Hackers Club 
Blog: 
PGP Fingerprint: 178A BF04 23F0 2BF5 535D  4A57 FD53 FD31 98DC 4E57
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkre6zEACgkQ/VP9MZjcTldwwwCeI5kVxUzAqRV13PzoaFfCHVsE
wRwAoMz8jPJbqqscIb+izg5RbkNBsMVW
=61oR
-END PGP SIGNATURE-
___
Web-SIG mailing list
Web-SIG@python.org
Web SIG: http://www.python.org/sigs/web-sig
Unsubscribe: 
http://mail.python.org/mailman/options/web-sig/archive%40mail-archive.com