Smalltalk › Cincom › VisualWorks

[7.7] No way to disable SeasideServer creation

‹ Previous Topic Next Topic ›
 
classic Classic list List threaded Threaded
♦
♦
 5 messages Options
Boris Popov, DeepCove Labs (SNN)
Reply | Threaded
Open this post in threaded view
♦
♦
|

[7.7] No way to disable SeasideServer creation

Boris Popov, DeepCove Labs (SNN)

Opentalk.SeasideServer class>>current

   ^current ifNil: [current := self newDefaultAt: self defaultPortNumber]

 

In the above, there is no way to ensure that SeasideServer does not get created in a given environment, even if you reset current to be nil, it'll get lazily created for you. It would be nice to have that option (previously you could set new server block to suppress adaptor creation).

 

Regards,

 

-Boris

 

--

DeepCove Labs Ltd.

+1 (604) 689-0322

4th floor, 595 Howe Street

Vancouver, British Columbia

Canada V6C 2T5

http://tinyurl.com/r7uw4

 

PacNet Services (Europe) Ltd.

+353 (0)61 714-360

Shannon Airport House, SFZ

County Clare, Ireland

http://tinyurl.com/y952amr

 

CONFIDENTIALITY NOTICE

 

This email is intended only for the persons named in the message header. Unless otherwise indicated, it contains information that is private and confidential. If you have received it in error, please notify the sender and delete the entire message including any attachments.

 

Thank you.

 


_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc
Michael Lucas-Smith-2
Reply | Threaded
Open this post in threaded view
♦
♦
|

Re: [7.7] No way to disable SeasideServer creation

Michael Lucas-Smith-2
I don't quite understand what you're asking for here...

Michael

On 4/28/10 8:02 AM, Boris Popov, DeepCove Labs (YVR) wrote:

Opentalk.SeasideServer class>>current

   ^current ifNil: [current := self newDefaultAt: self defaultPortNumber]

 

In the above, there is no way to ensure that SeasideServer does not get created in a given environment, even if you reset current to be nil, it'll get lazily created for you. It would be nice to have that option (previously you could set new server block to suppress adaptor creation).

 

Regards,

 

-Boris

 

--

DeepCove Labs Ltd.

+1 (604) 689-0322

4th floor, 595 Howe Street

Vancouver, British Columbia

Canada V6C 2T5

http://tinyurl.com/r7uw4

 

PacNet Services (Europe) Ltd.

+353 (0)61 714-360

Shannon Airport House, SFZ

County Clare, Ireland

http://tinyurl.com/y952amr

 

CONFIDENTIALITY NOTICE

 

This email is intended only for the persons named in the message header. Unless otherwise indicated, it contains information that is private and confidential. If you have received it in error, please notify the sender and delete the entire message including any attachments.

 

Thank you.

 


_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc


_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc
Boris Popov, DeepCove Labs (SNN)
Reply | Threaded
Open this post in threaded view
♦
♦
|

Re: [7.7] No way to disable SeasideServer creation

Boris Popov, DeepCove Labs (SNN)
In reply to this post by Boris Popov, DeepCove Labs (SNN)
I want to be able to set current to nil w/o it lazy initializing again on the next #current send.

-Boris (via BlackBerry)

From: [hidden email] <[hidden email]>
To: [hidden email] <[hidden email]>
Sent: Wed Apr 28 17:12:34 2010
Subject: Re: [vwnc] [7.7] No way to disable SeasideServer creation

I don't quite understand what you're asking for here...

Michael

On 4/28/10 8:02 AM, Boris Popov, DeepCove Labs (YVR) wrote:

Opentalk.SeasideServer class>>current

   ^current ifNil: [current := self newDefaultAt: self defaultPortNumber]

 

In the above, there is no way to ensure that SeasideServer does not get created in a given environment, even if you reset current to be nil, it'll get lazily created for you. It would be nice to have that option (previously you could set new server block to suppress adaptor creation).

 

Regards,

 

-Boris

 

--

DeepCove Labs Ltd.

+1 (604) 689-0322

4th floor, 595 Howe Street

Vancouver, British Columbia

Canada V6C 2T5

http://tinyurl.com/r7uw4

 

PacNet Services (Europe) Ltd.

+353 (0)61 714-360

Shannon Airport House, SFZ

County Clare, Ireland

http://tinyurl.com/y952amr

 

CONFIDENTIALITY NOTICE

 

This email is intended only for the persons named in the message header. Unless otherwise indicated, it contains information that is private and confidential. If you have received it in error, please notify the sender and delete the entire message including any attachments.

 

Thank you.

 


_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc


_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc
Michael Lucas-Smith-2
Reply | Threaded
Open this post in threaded view
♦
♦
|

Re: [7.7] No way to disable SeasideServer creation

Michael Lucas-Smith-2
If something is sending it, I think I'd hazard a guess and say that returning nil at that point would raise an error, right?

Michael

On 4/28/10 6:47 PM, Boris Popov, DeepCove Labs (YVR) wrote:
I want to be able to set current to nil w/o it lazy initializing again on the next #current send.

-Boris (via BlackBerry)

From: [hidden email] [hidden email]
To: [hidden email] [hidden email]
Sent: Wed Apr 28 17:12:34 2010
Subject: Re: [vwnc] [7.7] No way to disable SeasideServer creation

I don't quite understand what you're asking for here...

Michael

On 4/28/10 8:02 AM, Boris Popov, DeepCove Labs (YVR) wrote:

Opentalk.SeasideServer class>>current

   ^current ifNil: [current := self newDefaultAt: self defaultPortNumber]

 

In the above, there is no way to ensure that SeasideServer does not get created in a given environment, even if you reset current to be nil, it'll get lazily created for you. It would be nice to have that option (previously you could set new server block to suppress adaptor creation).

 

Regards,

 

-Boris

 

--

DeepCove Labs Ltd.

+1 (604) 689-0322

4th floor, 595 Howe Street

Vancouver, British Columbia

Canada V6C 2T5

http://tinyurl.com/r7uw4

 

PacNet Services (Europe) Ltd.

+353 (0)61 714-360

Shannon Airport House, SFZ

County Clare, Ireland

http://tinyurl.com/y952amr

 

CONFIDENTIALITY NOTICE

 

This email is intended only for the persons named in the message header. Unless otherwise indicated, it contains information that is private and confidential. If you have received it in error, please notify the sender and delete the entire message including any attachments.

 

Thank you.

 


_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc



_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc
Boris Popov, DeepCove Labs (SNN)
Reply | Threaded
Open this post in threaded view
♦
♦
|

Re: [7.7] No way to disable SeasideServer creation

Boris Popov, DeepCove Labs (SNN)
In reply to this post by Boris Popov, DeepCove Labs (SNN)
Not really, no. In fact, if something is sending it, having it return nil is a perfectly valid way of finding out where that happens (aside from simply looking at senders of course). We configure the same server image for different deployment scenarios and in some of them it is important to make sure that Seaside isn't running and having no adaptor is a good way of ensuring that (we do something similar for webtoolkit adaptors). I added an override of #current to suppress lazy initialization, so I'm perfectly happy, was simply suggesting that for some advanced users it would be nice to have some way of achieving this w/o such override.

-Boris (via BlackBerry)

From: Michael Lucas-Smith <[hidden email]>
To: Boris Popov, DeepCove Labs (YVR)
Cc: [hidden email] <[hidden email]>
Sent: Wed Apr 28 18:51:06 2010
Subject: Re: [vwnc] [7.7] No way to disable SeasideServer creation

If something is sending it, I think I'd hazard a guess and say that returning nil at that point would raise an error, right?

Michael

On 4/28/10 6:47 PM, Boris Popov, DeepCove Labs (YVR) wrote:
I want to be able to set current to nil w/o it lazy initializing again on the next #current send.

-Boris (via BlackBerry)

From: [hidden email] [hidden email]
To: [hidden email] [hidden email]
Sent: Wed Apr 28 17:12:34 2010
Subject: Re: [vwnc] [7.7] No way to disable SeasideServer creation

I don't quite understand what you're asking for here...

Michael

On 4/28/10 8:02 AM, Boris Popov, DeepCove Labs (YVR) wrote:

Opentalk.SeasideServer class>>current

   ^current ifNil: [current := self newDefaultAt: self defaultPortNumber]

 

In the above, there is no way to ensure that SeasideServer does not get created in a given environment, even if you reset current to be nil, it'll get lazily created for you. It would be nice to have that option (previously you could set new server block to suppress adaptor creation).

 

Regards,

 

-Boris

 

--

DeepCove Labs Ltd.

+1 (604) 689-0322

4th floor, 595 Howe Street

Vancouver, British Columbia

Canada V6C 2T5

http://tinyurl.com/r7uw4

 

PacNet Services (Europe) Ltd.

+353 (0)61 714-360

Shannon Airport House, SFZ

County Clare, Ireland

http://tinyurl.com/y952amr

 

CONFIDENTIALITY NOTICE

 

This email is intended only for the persons named in the message header. Unless otherwise indicated, it contains information that is private and confidential. If you have received it in error, please notify the sender and delete the entire message including any attachments.

 

Thank you.

 


_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc



_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc
Free forum by Nabble Edit this page